Enhancing Java Applications for the Cloud
summary
Demos compare three concrete approaches: enabling shared class cache cuts class-load work and can shave JVM footprint up to ~20%, static native images start under ~100 ms but lose JVM dynamism, and CRIU checkpoint/restore plus an instant on workflow resumes JVMs in ~100–260 ms (example: 3.9 s → 260 ms, ~18x faster) with small app code changes. A jit server centralizes compilation, shortens ramp-up in memory-constrained nodes and yields ~30% total memory savings in one scenario; latency under 1 ms is ideal.
AI-written summary · about
chapters (4)
related talks
53mThe Next Evolution of Java: ☕️ Achieving Hyper Performance and Efficiency in Cloud Native Workloads
42mSimple tweaks to get the most out of your JVM
40mHigh-Performance Java-Cloud-Native Apps & Microservices
01h 03mKeeping Your Java Hot.
46mMonolith to Serverless - Can Modern Cloud-Native Java Runtimes Do It All
24mJITServer: Disaggregated Caching JIT Compiler for the JVM in the Cloud
42mTechniques for a faster JVM start-up
01h 03mCloud Cost Optimization for Java Developers