How to Eliminate Java Performance Warmup
summary
Compares four concrete techniques and when each actually delivers: Graal Native Image AOT gives instant startup but typically lower peak performance because it cannot use runtime speculative optimizations that account for ~50% of JIT gains; ReadyNow JIT profile cache records loaded classes, initialized classes, profiling data, deoptimizations and compiled code to restore ~98% of warmed performance on restart; JIT-as-a-Service moves compilation off-node to improve throughput and reduce per-instance CPU; CRaC checkpoint restore resumes whole process state and cuts startup from seconds to tens of milliseconds.
AI-written summary · about
chapters (7)
- 0:00Java performance warmup
- 2:52AOT compilation limits
- 11:51When AOT makes sense
- 12:32Storing JIT with ReadyNow
- 15:44Decoupling JIT from JVM
- 21:42Saving state with CRaC
- 25:38Choosing warmup solution
related talks
01h 03mKeeping Your Java Hot.
46mKeeping Your Java Hot by Solving the JVM Warmup Problem
54mKeeping Your Java Hot by Solving the JVM Warmup Problem
50mAOT or JIT: Faster Startup or Faster Code?
38mAOT or JIT: Faster Startup or Faster Code?
56mKeeping Your #Java Hot by Solving the #JVM Warmup Problem
50mBinary Java: CDS, CRaC and AOT for faster JVM startup and warmup
42mTechniques for a faster JVM start-up