JEP draft: Compact Object Headers by Default
| Author | rkennke |
| Owner | Roman Kennke |
| Type | Feature |
| Scope | JDK |
| Status | Draft |
| Component | hotspot / runtime |
| Discussion | hotspot dash runtime dash dev |
| Effort | XS |
| Duration | XS |
| Created | 2025/07/01 13:36 |
| Updated | 2025/07/14 14:55 |
| Issue | 8361187 |
Summary
Make compact object headers the default object header layout, and deprecate the old 12-byte object header layout, with the intention to remove the old layout in a future release.
Non-Goals
It is not a goal to completely remove/obsolete the old 12-byte object header layout at this time.
Motivation
Compact object headers were introduced as an alternative object-header layout by JEP 450 in JDK 24, and turned into a full product feature by JEP 519 in JDK 25. Features of this size are best introduced carefully and gradually, so we have not turned it on by default, yet.
Since JDK 24, compact object headers have proven their stability and performance.
They have been tested at Oracle by running the full JDK test suite. They have also been tested at Amazon by hundreds of services in production, most of them using backports of the feature to JDK 21 and JDK 17.
Various experiments demonstrate that enabling compact object headers improves performance:
- In one setting, the SPECjbb2015 benchmark uses 22% less heap space and 8% less CPU time.
- In another setting, the number of garbage collections done by SPECjbb2015 is reduced by 15%, with both the G1 and Parallel collectors.
- A highly parallel JSON parser benchmark runs in 10% less time.
It is time to make compact object headers the default mode of operation and deprecate the old object header layout.
Description
Compact object headers are enabled in JDK 25 via the command-line options
$ java -XX:+UseCompactObjectHeaders ...That option, -XX:+UseCompactObjectHeaders, will no longer be needed once they are the default. Instead, if, for any reason, the feature needs to be turned off, it can be done by running with:
$ java -XX:-UseCompactObjectHeaders ...Testing
Compact object headers were subjected to massive testing as part of JEP 450 and JEP 519. No further testing is required.
Risks and Assumptions
As discussed in JEP 450, future features may require additional object-header bits. We have already reserved four bits for Project Valhalla. If a need for even more bits arises then we can shrink compressed class pointers and identity hash codes even further, using techniques we have already prototyped in Project Lilliput.
