JDK 27: A Performance-Focused Non-LTS Release
JDK 27 is a non-LTS Java release that focuses on performance optimization by targeting new capabilities such as the Vector API, Compact Object Headers by default, and the G1GC garbage collector as the universal default across environments. These JDK 27 features are being finalized as the platform approaches a feature freeze, with the release schedule moving through two rampdown phases, followed by release candidates and general availability. According to InfoQ, JDK 27 will be the second non-LTS release since JDK 25 and already includes ten JEPs in its feature set so far. For Java developers and enterprises, the headline changes translate into better data-parallel execution, reduced memory overhead, and simpler garbage collection tuning, tightening Java’s position as a high-performance runtime for both new and existing workloads.
Vector API in Java: SIMD for Data-Parallel Workloads
The Vector API Java developers have been watching for several releases moves forward again in JDK 27 via JEP 537, "Vector API (Twelfth Incubator)." This twelfth incubation continues the work started in JDK 16, offering an API to express vector computations that compile at runtime to optimal SIMD instructions on supported CPUs. The goal is to deliver performance superior to equivalent scalar computations for data-parallel workloads such as numerical analytics, image processing, or machine learning inference. The implementation remains largely unchanged since JDK 25, which helps stabilize expectations for early adopters. The Vector API will stay in incubator status until Project Valhalla features can be used in a future preview, at which point the API and its implementation are expected to evolve again. For teams doing Java performance optimization, this means more predictable, portable SIMD acceleration without hand-written platform-specific intrinsics.
Compact Object Headers: Memory Efficiency by Default
JEP 534 proposes to enable Compact Object Headers by default in HotSpot, building on JEP 519, which shipped the feature in JDK 25. Compact Object Headers change the layout of object headers to reduce per-object overhead, freeing heap space and improving cache locality. For large-scale applications with many small objects, the impact can be significant: more objects fit into the same memory footprint, and the garbage collector can process heaps more efficiently. In JDK 27, this behavior becomes the standard rather than an opt-in, so most applications will gain the benefit without configuration changes. Developers who previously tuned for older header layouts may want to re-check profiling baselines, but for most workloads this shift should be transparent. Together with the Vector API, Compact Object Headers show how JDK 27 features address both CPU and memory aspects of Java performance optimization.
G1GC as the Default Garbage Collector Everywhere
The G1GC garbage collector has long been the default on server-class configurations, but JEP 523 extends that choice to all environments in JDK 27. Under this proposal, if no garbage collector is specified on the command line, the G1GC garbage collector will always be selected by the HotSpot JVM. This change simplifies operational decisions, giving a consistent default across desktops, containers, and smaller devices. G1GC’s design targets predictable pause times and decent throughput for a wide range of heap sizes, which makes it a practical baseline for most applications. Teams that rely on other collectors can still configure them explicitly, but new deployments and many existing ones can standardize on G1GC without extra tuning. When combined with Compact Object Headers, this default helps improve garbage collection behavior while keeping JVM configuration simpler for developers and operators.
Release Timeline and Broader JDK 27 Ecosystem
JDK 27’s release schedule, approved by Mark Reinhold, sets Rampdown Phase One for June 4, 2026, Rampdown Phase Two for July 16, 2026, an initial release candidate on August 6, 2026, a final release candidate on August 20, 2026, and general availability on September 14, 2026. Alongside the Vector API, Compact Object Headers, and G1GC changes, several other JEPs are shaping the release: PEM encodings of cryptographic objects, JFR in-process data redaction, and post-mortem crash analysis with jcmd are all proposed to target JDK 27. While JEP 528’s status may shift toward JDK 28, the overall feature set underscores OpenJDK’s direction: refine performance, improve observability, and reduce operational friction. For enterprises planning upgrades, JDK 27 offers a chance to trial these performance-oriented changes ahead of future LTS releases while keeping the option to stay on existing long-term support lines.
