Maximizing Performance with GraalVM
summary
GraalVM runs Java two ways: the Graal JIT yields higher throughput and can optimize through layers of abstraction so an objects.hash version performs like a hand‑written loop thanks to partial escape analysis. Native image ahead‑of‑time compilation produces snapshots that start in milliseconds (demo shows ~25 ms startup) and cut total process memory (example ~32 MB footprint versus ~150–170 MB for JIT), integrates with Micronaut/Quarkus/Spring tooling, and requires explicit configs for reflection and dynamic class loading.
AI-written summary · about
chapters (7)
- 0:00Introduction to GraalVM
- 7:29Running Java with GraalVM JIT
- 21:05Benchmarking Java performance
- 34:33Ahead-of-time compilation with Native Image
- 48:44Demo of Native Image in action
- 51:18GraalVM ecosystem and use cases
- 55:59Q&A
related talks
20mMaximizing Java Application Performance with GraalVM
52mMaximizing Performance With GraalVM
45mMaximizing performance with GraalVM
59mMaximizing performance with GraalVM
03h 07mEverything you need to know about GraalVM
33mNew Opportunities for Developers with GraalVM
51mAbstractions Without Regret with GraalVM
44mJava In The Cloud with GraalVM
