From Cold Starts to Escape Velocity: Three Practical Ways to Accelerate Java Services
summary
Service cold start is ~5.6–6 seconds with a layered Spring Boot image, reduced to under 2 seconds by using AOT cache (Project Leyden) with no code changes, pushed to under 1 second by building a GraalVM Native Image at the cost of minutes and gigabytes of build resources and extra reflection/JFR config, and shrunk to ~80 ms by using CRaC checkpoint/restore which preserves JVM optimizations but requires vendor support, code hooks for non‑serializable resources and careful snapshot security.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 3:12Faster Java startup
- 7:44AOT cache optimization
- 13:31GraalVM native image
- 23:50CRaC instant restarts
- 37:29Recap and path
- 38:56Q&A
related talks
45mFour Approaches to Reducing Java Startup Time: AppCDS, Native Image, Project Leyden, CRaC
52mTechniques for a faster JVM start-up
42mTechniques for a faster JVM start-up
46mReduce Cold Starts for Java Serverless Applications in AWS
38mAfraid of Java cold starts in Serverless? Fear not, Java is super fast!
51mHow To Reduce Cold Starts for Java Serverless Applications in AWS
53mFour Approaches to Reducing Java Startup Time
51mAfraid of Java Cold Starts in Serverless? Fear Not, Java is Super Fast!