Keeping Your #Java Hot by Solving the #JVM Warmup Problem
summary
Explains concrete fixes and measurements: generate and reuse a ReadyNow profile (classes, init state, profiling, compiled code) to reach ~97–98% of warmed performance on restart; OpenJDK Project Leyden adds AOT class loading plus future method-profiling/AOT code caching; decouple compilation with JIT-as-a-Service to cache and further optimize compiled methods (measured ~20% higher throughput with faster warmup); full-process CRaC checkpointing restores apps (Spring Boot 4s → 38ms, Micronaut ~1s → 46ms, Quarkus ~1s → 33ms).
AI-written summary · about
chapters (10)
- 0:00Introduction to Azul and JVM warmup
- 8:21Understanding JVM warmup problem
- 12:18Ahead-of-time compilation approach
- 25:02When to use AOT compilation
- 26:07Storing JIT compilation data with ReadyNow
- 33:00Decoupling JIT compiler from JVM
- 43:00Combining ReadyNow and cloud compiler
- 44:03Checkpointing entire application state
- 51:30Summary of solutions and trade-offs
- 52:57Q&A on CI/CD and warmup detection
related talks
54mKeeping Your Java Hot by Solving the JVM Warmup Problem
46mKeeping Your Java Hot by Solving the JVM Warmup Problem
01h 03mKeeping Your Java Hot.
27mHow to Eliminate Java Performance Warmup
42mTechniques for a faster JVM start-up
45mWarming up the JVM: CRaC and other tricks
46mSimple Tweaks to Get the Most Out of Your JVM
06mSimple Tweaks to Get the Most Out of your JVM