JDK 27 released with compact object headers and G1 GC as default cutting heap use 10-20%

JDK 27 delivers two concrete performance improvements that apply immediately to existing applications. Compact object headers (JEP 534) reduce the per-object memory overhead from 96 bits to 64 bits, which directly lowers heap usage by 10-20% and can improve throughput by 5-10%. These gains appear without any code changes, making the upgrade a straightforward performance win for most workloads. The change is transparent to developers, but operators should expect lower memory pressure in containers and reduced garbage collection frequency.

The second change, G1 GC becoming the default collector on all platforms (JEP 523), removes the previous distinction between small and large heaps. Applications running in constrained environments that previously relied on Serial GC may now experience longer pause times or higher CPU usage unless explicitly reconfigured. Engineers should verify the impact on their smallest containers before rolling out JDK 27, as the new default may not be optimal for all low-memory scenarios. The change simplifies garbage collection tuning guidance but requires attention to edge cases.

Beyond these two defaults, JDK 27 contains nine JEPs, all either preview features or targeted improvements that do not require immediate adoption. This release follows the established six-month cadence, meaning no breaking changes for production code unless preview features are explicitly enabled. The lack of mandatory migrations makes JDK 27 a low-risk upgrade for most teams, though those on older LTS versions (8 or 11) are encouraged to begin a step-by-step migration rather than attempting a direct jump. The release emphasizes incremental improvements over disruptive changes.

The broader Java ecosystem continues to evolve around JDK 27, with related updates in tooling and frameworks. IntelliJ IDEA now supports Java and Kotlin intelligence in VS Code and other LSP-based editors, which may influence IDE choice for teams using multiple languages. Meanwhile, Project Valhalla and a proposed simple JSON API signal future directions for Java, though neither is ready for production use. Engineers should focus on the immediate performance benefits of JDK 27 while monitoring these longer-term initiatives for potential future adoption.