Techniques for a faster JVM start-up
summary
Cold-start techniques create and reuse JVM artifacts to cut first-response time: generating a dynamic CDS hive for OpenJDK reduces a Spring PetClinic cold start from ~7s to ~6s (≈15%), enabling reuse but suffering classpath, platform and JDK-version constraints; enabling OpenJ9 shared class cache (stores JIT code too) cuts the same case to ~4.2–4.5s; compiling to a GraalVM native image produces a native binary that starts in ~20–85 ms. All artifacts run, but portability and build-time/config complexity vary.
AI-written summary · about
chapters (8)
- 0:00Start
- 0:41Agenda
- 3:41Startup Time
- 5:51Hot Startup
- 13:48Dynamic Cds
- 17:04Lambda Proxy Classes
- 33:23Eclipse Open G9
- 36:07Share Class Cache
related talks
42mTechniques for a faster JVM start-up
46mSimple Tweaks to Get the Most Out of Your JVM
06mSimple Tweaks to Get the Most Out of your JVM
01h 03mKeeping Your Java Hot.
40mFrom Cold Starts to Escape Velocity: Three Practical Ways to Accelerate Java Services
45mFour Approaches to Reducing Java Startup Time: AppCDS, Native Image, Project Leyden, CRaC
42mSimple tweaks to get the most out of your JVM
53mFour Approaches to Reducing Java Startup Time