Keeping Your Java Hot by Solving the JVM Warmup Problem
summary
Shows concrete fixes and measured tradeoffs: Graal native image removes warmup but loses speculative JIT gains; decoupling compilation into a cloud JIT-as-a-Service (using Falcon/LLVM) caches compiled methods and reduces per-instance CPU spikes; profiling+replay via Ready Now boots instances to ~98% of warmed performance. Checkpointing with Project CRaC restores full heap and JIT state, turning ≈4s to first transaction into ≈40ms (roughly two orders of magnitude).
AI-written summary · about
chapters (9)
- 0:00Introduction
- 0:23JVM warmup problem
- 7:46Ahead of time compilation
- 11:59Speculative optimizations
- 20:48Storing JIT compilation data
- 23:55Decoupling JIT compiler
- 32:46Checkpointing JVM state
- 40:33Comparing solutions
- 42:16Q&A
related talks
54mKeeping Your Java Hot by Solving the JVM Warmup Problem
01h 03mKeeping Your Java Hot.
56mKeeping Your #Java Hot by Solving the #JVM Warmup Problem
27mHow to Eliminate Java Performance Warmup
45mWarming up the JVM: CRaC and other tricks
06mSimple Tweaks to Get the Most Out of your JVM
46mSimple Tweaks to Get the Most Out of Your JVM
42mSimple tweaks to get the most out of your JVM