Where Did the Saved Bytes Go? Compact Object Headers in IntelliJ IDEA - The JetBrains Blog
Blog post from JetBrains
Compact object headers, enabled by default in Java 27 through Project Lilliput, reduce HotSpot’s standard 12-byte object header to 8 bytes, potentially lowering the cost of applications that create millions of objects. Tests in IntelliJ IDEA across an empty welcome screen, the Spring Petclinic project, and the large IntelliJ IDEA monorepo found that although overall resident set size showed no consistent improvement at identical heap limits, modeled live-object footprints fell by roughly 6.3% to 8.4%, depending on object shapes, field alignment, and padding. Under repeated IDE workloads, compact headers reduced total allocation volume by 8.8% for Petclinic and 13.0% for the monorepo, generally accompanied by fewer garbage-collection events and modest reductions in GC time. Operation latency and throughput improvements were small and variable, but the feature enabled lower reliably usable heap ceilings, reducing the monorepo’s tested minimum -Xmx by 320 MiB, or 17%. The results indicate that compact headers provide real heap-level and allocation benefits without application code changes, but their effect on process memory and performance must be measured separately because RSS also includes substantial non-heap memory and not every object becomes smaller.
| Trend | Post Mentions | Total Month Mentions | Posts | Companies | MoM |
|---|---|---|---|---|---|
| AI Agents | 1 | 5,564 | 1,101 | 236 | -21% |
Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.