A Developer's Perspective On Greener Future: GreenOps in practice
summary
Practical claims and tools: Thoughtworks and the Green Software Foundation push GreenOps with an estimate-driven measurement stack and concrete wins. Cloud Carbon Footprint is used to convert cloud usage into kWh and CO2 (Etsy cut emissions by moving workloads), Kepler attributes real power to Kubernetes pods, and cloud PUEs drop from ~1.4 to ~1.1 yielding ~20% savings. Concrete numbers include servers consuming ~25% idle power, language energy factors (Python ~70x vs C, Java ~2x), and model training like Stable Diffusion’s 150,000 GPU hours ≈ 11–14 tCO2. Tools highlighted: Cloud Carbon Footprint, Kepler, and the 1.1 vs 1.4 PUE comparison.
AI-written summary · about
chapters (7)
- 0:00Introduction and keynote setup
- 3:58Sustainability of IT explained
- 16:18Carbon efficiency concepts
- 24:04Carbon awareness strategies
- 36:15GreenOps and FinOps overlap
- 46:25AI and machine learning efficiency
- 50:14Q&A session
related talks
42mUndertaking a GreenOps Approach in the Public Cloud
06mEco-DevOps - Building a Greener Future
26mGoing Green: The Future of Sustainable Software
41mWriting Greener Software Even When You Are Stuck On-Prem
34mSustainable Software Engineering, Building Carbon-Efficient Applications
32mGreenOps in the cloud
35mSustainable Platform Engineering: Having a Green Thumb Without Shooting Up
49mArchitecting for Sustainability: A Software Architects Guide to Green Software Keynote