<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Aot on Devops Monk</title><link>https://devops-monk.com/tags/aot/</link><description>Recent content in Aot on Devops Monk</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 10 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://devops-monk.com/tags/aot/index.xml" rel="self" type="application/rss+xml"/><item><title>AOT Compilation in Java 25 (JEP 514 &amp; 515): Faster Startup, Zero Warm-Up</title><link>https://devops-monk.com/tutorials/java25/aot-compilation/</link><pubDate>Sun, 10 May 2026 00:00:00 +0000</pubDate><guid>https://devops-monk.com/tutorials/java25/aot-compilation/</guid><description>The Java Startup Problem Java&amp;rsquo;s performance story has always had one weak spot: startup time.
When a JVM starts, it:
Loads and verifies class bytecode Interprets bytecode (slow) Profiles which methods are called most (warm-up) Compiles hot methods to native code via JIT (takes time and CPU) Eventually reaches peak throughput This process takes seconds for large applications. For a Spring Boot application, typical warm-up to peak throughput can take 10–30 seconds.</description></item></channel></rss>