Scotty, I need Warp Speed - Ways to improve JVM startup
summary
JVM startup bottlenecks center on class loading (the JVM loads ~1,200 classes; frameworks can add tens of thousands), interpretation and tiered JIT warm‑up. Measured numbers: fat Spring Boot jar ~3.2s, exploded jar saves ~1s, Project Leyden ~1.3s (8 cores ~0.9s), GraalVM native image ~0.5s (community) to ~0.28s (enterprise), and CRaC checkpoint resumes warmed state in ~100–500ms. ReadyNow uses persisted compile logs to skip C1/C2 warm‑up; JIT server centralizes compilation for many containers.
AI-written summary · about
chapters (13)
- 0:00Introduction to JVM startup
- 1:08Understanding JVM startup and warm-up
- 8:28Execution engine and compilation process
- 19:26Solutions for faster JVM startup
- 21:10Class Data Sharing and AppCDS
- 22:15Project Leyden overview
- 26:30Native Image with GraalVM
- 29:42CRaC for fast JVM recovery
- 31:28ReadyNow for warm-up optimization
- 34:18Cloud Native Compiler and JIT Server
- 38:13Performance test results comparison
- 44:40Choosing the right solution for your needs
- 47:11Q&A and summary
related talks
42mTechniques for a faster JVM start-up
54mKeeping Your Java Hot by Solving the JVM Warmup Problem
01h 03mKeeping Your Java Hot.
53mFour Approaches to Reducing Java Startup Time
26mGoing Serverless With Spring’s Support for GraalVM, Project CraC & More
45mFour Approaches to Reducing Java Startup Time: AppCDS, Native Image, Project Leyden, CRaC
56mKeeping Your #Java Hot by Solving the #JVM Warmup Problem
59mRuntime Efficiencies and Spring Boot