This article evaluates the impact of Project Lilliput's compact object headers on memory usage within the IntelliJ IDEA IDE. It examines how compressing 12-byte headers into 8-byte words affects heap footprint and garbage collection across varied workloads. The findings clarify that while object footprints shrink, overall process resident set size (RSS) improvements depend on specific object mix and alignment, advising caution in adjusting heap limits.
Key points
Compact object headers compress the standard 12-byte Java object header into a single 8-byte word.
The memory savings from smaller headers are not uniform and depend heavily on individual object layout and memory alignment.
Reduced object size can lead to lower allocation churn and decreased garbage collection pressure.
Actual process RSS reduction may not match the theoretical savings in object header size.
Measurements of memory impact should be taken independently rather than assuming automatic improvements in overall application performance.