Lambda SnapStart – CRaC’ing the cold start
summary
Lambda SnapStart snapshots a warmed JVM heap for published Lambda versions so subsequent cold starts restore a snapshot instead of redoing classloading and JIT, cutting a Spring Boot example from ~7s cold start to ~1s (benchmarks show ~536ms after priming, ~<500ms with extra hooks). Configuration uses the Lambda version/alias model and infra-as-code flags (for example apply on published versions in SAM/CDK). Hooks implement org.crac.resource for pre-snapshot hook and post-restore work; beware network retries, ephemeral secrets and java.util.Random.
AI-written summary · about
chapters (9)
- 0:00Introduction to SnapStart
- 1:51Java in serverless applications
- 3:58Cold start problem in Lambda
- 9:18How Lambda SnapStart works
- 12:16Configuring SnapStart
- 18:39Demo and live results
- 24:02Considerations and limitations
- 27:09Performance improvements data
- 29:13Q&A and resources
related talks
40mAWS Lambda SnapStart: Dramatically reduce cold starts for your Java functions
46mReduce Cold Starts for Java Serverless Applications in AWS
46mThawing Java on AWS Lambda Reducing Cold Start Times from 11 Seconds to 1
51mHow To Reduce Cold Starts for Java Serverless Applications in AWS
44mHow to develop, run and optimize Spring Boot 3 application on AWS Lambda
07m#BuildPropulsionLab at #DevoxxUK: @jbaruch with Mark Sailes
34mThawing Java on AWS Lambda
53mHigh performance Serverless Java on AWS