Everything you need to know about GraalVM
summary
GraalVM claims a single runtime for JVM languages plus JavaScript, Python, R and Ruby, with concrete numbers: the JIT eliminates boxing and array allocations to turn an Objects.hash microbenchmark from 4x slower on HotSpot to parity on GraalVM Community Edition; the native-image flow produces tiny binaries that start in native image startup 20–50 ms and run Micronaut in ~12–15 MB resident RAM in demos. Trade-offs are explicit: closed‑world AOT needs reflection/resource config (use the native-image tracing agent), and polyglot Node.js/Java interop and VisualVM/debugger support are production-ready.
AI-written summary · about
chapters (10)
- 0:00Start
- 12:26download the binaries
- 19:07calculating hash codes
- 24:49inline the hash method
- 38:02register allocation
- 55:45add additional workloads
- 1:05:52compile your applications ahead of time using the native image utility
- 1:38:18use the flag trace class initialization
- 1:57:12apply some load to the applications
- 2:07:51measure cpu time
related talks
17mGraalVM Runtime Efficiency and Contributing to the Development Community
56mMaximizing Performance with GraalVM
50mGraalVM for Java developers
47mJava and the GraalVM
59mGraalVM: Run Programs Faster Anywhere
50mOne VM to Rule Them All
33mNew Opportunities for Developers with GraalVM
20mGraalVM: Run Programs Faster Anywhere
