<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>JEP450 on JAVAPRO International</title><link>https://javapro-en.svenruppert.com/tags/jep450/</link><description>Recent content in JEP450 on JAVAPRO International</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Tue, 10 Feb 2026 07:00:01 +0000</lastBuildDate><atom:link href="https://javapro-en.svenruppert.com/tags/jep450/index.xml" rel="self" type="application/rss+xml"/><item><title>Mastering Memory Efficiency with Compact Object Headers in JDK 25</title><link>https://javapro-en.svenruppert.com/mastering-memory-efficiency-with-compact-object-headers-in-jdk-25/</link><pubDate>Tue, 10 Feb 2026 07:00:01 +0000</pubDate><guid>https://javapro-en.svenruppert.com/mastering-memory-efficiency-with-compact-object-headers-in-jdk-25/</guid><description>&lt;p&gt;Compact Object Headers are introduced in JDK 25 through JEP 519, marking a significant step forward for memory optimization in the JVM. First introduced experimentally in JEP 450 with JDK 24, this feature, authored by Roman Kennke, reduces the per-object memory footprint without slowing down performance. &lt;/p&gt;
&lt;p&gt;The payoff is especially clear in object-heavy workloads and memory-constrained environments, such as those found in containers and cloud-native deployments.&lt;/p&gt;
&lt;p&gt;In JDK 25, Compact Object Headers graduate from experimental to standard. However, they’re not enabled by default. Developers must turn them on using JVM flags to see the benefits.&lt;/p&gt;</description></item><item><title>Java 24: A Story of Code, Conflict, and Conquer</title><link>https://javapro-en.svenruppert.com/java-24-a-story-of-code-conflict-and-conquer/</link><pubDate>Wed, 27 Aug 2025 07:00:03 +0000</pubDate><guid>https://javapro-en.svenruppert.com/java-24-a-story-of-code-conflict-and-conquer/</guid><description>&lt;p&gt;In a digital world far away from here, runs a Java application without problems. The logs are quiet, the servers are stable, and Emma and her team live in peace. But then, the first attack arrives! First innocent. A little spike in the memory use. But than another, and another. Within a couple of days, it turns into a disaster. Garbage collectors are going wild. The latency rises. The servers are shaking. The memory realm is flooded by invisible enemies: unnecessarily inflated object headers. They hide in every object, wasting valuable bytes and creating chaos in the heap.&lt;/p&gt;</description></item></channel></rss>