GraalVM, CRaC, Leyden and friends - in search of TRULY...
summary
GraalVM AOT and native-image, Project Leyden’s split pipeline (compile time, CDS generation, link time, runtime) and CRaC snapshots are presented as practical ways to cut cold starts: GraalVM ahead-of-time native-image hits roughly 80% of JIT peak performance, Galahad brings Graal into the JDK, and CRaC snapshots in AWS Lambda (SnapStart) restore preinitialized JVMs but require fixes like secure-random handling. Real-world telemetry shows only about one third of deployments set container JVM flags correctly, so CDS/ADB and Leyden pipelines matter.
AI-written summary · about
chapters (8)
- 0:00Introduction and speaker intro
- 3:00Cloud native Java definition
- 13:22Java standards and frameworks
- 17:56Cold start problem in Java
- 22:11GraalVM explained
- 30:06Other JVM runtime optimizations
- 37:58Project Leyden overview
- 41:54JDK 21 features and conclusion
related talks
41mGraalVM, CRaC, Leyden and friends - in search of TRULY cloud-native Java
03h 07mEverything you need to know about GraalVM
33mNew Opportunities for Developers with GraalVM
35mTop 10 Things to Do with GraalVM
26mGoing Serverless With Spring’s Support for GraalVM, Project CraC & More
53mScale up with GraalVM and AWS Lambdas
46mCRAC vs GraalVM
50mGraalVM for Java developers
