<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Optimization on JAVAPRO International</title><link>https://javapro-en.svenruppert.com/tags/optimization/</link><description>Recent content in Optimization on JAVAPRO International</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Wed, 18 Feb 2026 07:00:02 +0000</lastBuildDate><atom:link href="https://javapro-en.svenruppert.com/tags/optimization/index.xml" rel="self" type="application/rss+xml"/><item><title>the runtime illusion: what Java really runs</title><link>https://javapro-en.svenruppert.com/the-runtime-illusion-what-java-really-runs/</link><pubDate>Wed, 18 Feb 2026 07:00:02 +0000</pubDate><guid>https://javapro-en.svenruppert.com/the-runtime-illusion-what-java-really-runs/</guid><description>&lt;p&gt;&lt;figure class="post-figure"&gt;
 &lt;img src="https://javapro-en.svenruppert.com/uploads/2025/08/bluetab-capabilities-data-ai-products_cmyk300-1024x576.jpg" alt="" loading="lazy" decoding="async"&gt;
 
 
 
&lt;/figure&gt;
&lt;/p&gt;
&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;p&gt;Java&amp;rsquo;s bytecode is made abstract to be portable and neutral from specific hardware. Yet in production, it performs with the precision of native code. How? The secret lies in the JIT compiler, a near magical blend of static analysis and real-time insights. It reinterprets, restructures and often reinvents the code based on the runtime behaviour. This article traces that silent transformation using the Semeru (OpenJ9) JIT, following a method from source to bytecode to intermediate representation and ultimately to highly optimised machine code. You will be amazed to see how your logic is optimized beyond recognition. What you write is not always what runs, and what runs is often much better version of what you imagined.&lt;/p&gt;</description></item><item><title>Optimizing Spring Integration Tests at Scale</title><link>https://javapro-en.svenruppert.com/optimizing-spring-integration-tests-at-scale/</link><pubDate>Wed, 17 Dec 2025 07:00:02 +0000</pubDate><guid>https://javapro-en.svenruppert.com/optimizing-spring-integration-tests-at-scale/</guid><description>&lt;h2 id="1-introduction"&gt;1. Introduction&lt;/h2&gt;
&lt;p&gt;Sprint Boot is a popular Java framework that provides a rich platform for integration testing. It&amp;rsquo;s pretty convenient and flexible; however, at a large scale, when the project has hundreds or even thousands of integration tests using lots of heavy components (like TestContainers-managed beans), there can be performance and other issues. &lt;strong&gt;There are many hidden details that make much sense when the codebase becomes bigger and the configuration becomes more complicated.&lt;/strong&gt; In this article, we&amp;rsquo;ll look at how the framework works under the hood, why it can be slow and inefficient, and how to boost the performance.&lt;/p&gt;</description></item></channel></rss>