The Future is 💚: A Journey through the Energy Efficient ..
summary
Measured Java results from JDK 21 and multiple JVMs use real load tests two hours long against Spring PetClinic and a Quarkus sample with energy readings from powerstat / Intel RAPL and runtime metrics, showing native-image w/PG optimizations often cuts CPU energy but can reduce throughput unless tuned, and there is no consistent correlation between lower energy and better performance. Practical fixes that demonstrably save time or energy include Maven 3.9 build caching (minutes to seconds saved), Spring Boot caching, Caffeine or Hazelcast, websitecarbon and co2.js for frontend, and the repeated conclusion to measure per use case.
AI-written summary · about
chapters (10)
- 0:00Introduction to green coding
- 2:08Climate impact context
- 5:09Principles of green software
- 8:01Architectural strategies
- 10:36Build optimization tips
- 14:08Serverless and scaling
- 15:15JVM performance analysis
- 37:47Caching in application code
- 42:28Front-end optimization
- 45:39Key takeaways and conclusions
related talks
39mCreate an Eco-Friendly World with Green Software Engineering
50mEnergy Efficient Design Principles of Software Engineering
31mCreate an eco-friendly world with Green Software Engineering
28mBuilding Sustainable Software with Java
46mWriting Greener Java Applications
46mThe Efficiency Paradox: How to Save Yourself & the World
51mJava Performance Update: From JDK 21 to JDK 25
56mKeeping Your #Java Hot by Solving the #JVM Warmup Problem