"Cloud Cost Optimization for Java Developers"
summary
Claims immediate wins from switching to Graviton—typical 50% lower instance price and reported ~20% cost improvement for Java workloads—plus a high-performance JVM that is Prime and a drop-in build Zulu. Quantified tradeoffs: JIT warm-up often takes 10–20 minutes to reach ~90% efficiency, a one-time 7–10% price dip from Graviton-era VMs, and large waste from idle VMs; proposed fixes include dynamic cores, warmed images (Ready Now), and a cloud-native compiler that pushes JITs to many instances.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 3:32Cloud cost strategies for Java
- 5:41Compute pricing trends
- 8:52Graviton processors for cost savings
- 10:16Monolith vs microservices trade-offs
- 15:16Java efficiency and JVM optimizations
- 20:03JVM warm-up and CPU issues
- 27:46Garbage collection tips
- 31:55Reduce cloud waste steps
- 35:44Graviton and JVM benefits
- 36:49Managed services cost analysis
related talks
41mRunning Java on ARM - is it worth it?
58mEnhancing Java Applications for the Cloud
20mAtomics Habits in cost optimizations in the cloud
01h 02mJourney to Cloud : Leave No Java Workload Behind
33mOvercoming migration hurdles
01h 02mWhat’s new for Java in the Cloud?
51mProductivity, Sustainability, and Fun in modern Java
10m{ Fast, Cost-effective } – Choose Two