The Next Frontier in Open Source Java Compilers: Just-in-Time Compilation as a Service
summary
Separates the JIT compiler into a remote service so containers drop heavy CPU and memory spikes, enabling smaller images and faster ramp-up; OpenJ9 JITServer (distributed with IBM Samurai runtimes) runs on Linux for Java 8/11/17 and integrates with Kubernetes/OpenShift. Tests show roughly half memory footprint for clients and overall cluster memory down to ~66% with one JITServer; each server prefers 10–20 clients and 1–2 GB RAM. Instant-on snapshots hit ~300 ms startup and compilation costs amortize across instances.
AI-written summary · about
chapters (11)
- 0:00Open source Java compilers
- 1:09Java cloud challenges
- 4:01JVM and JIT limits
- 8:20JIT as a service
- 9:42OpenJ9 and JIT Server
- 12:55Container efficiency tests
- 15:31Live demo: JIT Server benefits
- 18:14Using JIT Server
- 21:03Open source vs proprietary
- 22:31Final thoughts
- 24:16Q&A
related talks
38mThe Next Frontier in Open Source Java Compilers: Just-In-Time Compilation as a Service
40mNext Frontier in Open Source Compilers: Just-In-Time Compilation as a Service
24mJITServer: Disaggregated Caching JIT Compiler for the JVM in the Cloud
01h 02mJourney to Cloud : Leave No Java Workload Behind
52mCloud Native JVM. Cloud Compiler
33mCloud Native Java with OpenJ9: Fast, lean and definitely mean
55mJIT and AOT in the JVM
57mCould your Java workloads be missing out on something?
