Going AOT: Everything you need to know about GraalVM for Java
summary
GraalVM’s native-image compiles Spring and microservices into platform-specific executables that start in ~48–56 ms and can be as small as ~37–111 MB; a Spring AI travel recommender calling OpenAI GPT‑4 is built and runs correctly. Benchmarks show ~50k RPS for native vs ~55k for warmed JVM, often achieving 3x-5x less memory and comparable peak throughput; native builds take ~45 s for a Spring app but support quick-build flags, PGO/profile-guided tuning and tools like native image, 50 ms startup for faster cold starts.
AI-written summary · about
chapters (10)
- 0:00Introduction to GraalVM
- 3:19GraalVM project history
- 6:32Native Image demo
- 18:58Native Image benefits
- 23:53Library compatibility with Native Image
- 28:47Testing and best practices
- 30:54Performance comparison
- 36:50Future of GraalVM
- 42:28Why use GraalVM
- 43:30Q&A session
related talks
51mGoing AOT: Everything you need to know about GraalVM for Java applications
45mGoing AOT: Everything you need to know about GraalVM for Java applications
51mAOT: Everything you need to know about GraalVM for Java applications
44mBring the Action: Using GraalVM in Production
46mBring the Action: Using GraalVM in Production
47mBring the action: using GraalVM in production
53mBootiful GraalVM
46mFast and Lightweight Spring Boot Applications with GraalVM