Green Must Be Convenient
summary
Practical claims and live tools determine value here: the session shows Azure SQL Database managing vast JSON objects to bridge data lakes and relational apps, quantifies efficiency with PUE 1.5 vs 1.1 for typical vs cloud data centers, and highlights embodied carbon like server embodied carbon ~4,000 kg and a smartphone ~8 kg. It demonstrates CPU nonlinearity (better to run servers hotter), describes implemented carbon‑aware scheduling on Kubernetes (a cabetes plugin) and reports modest but real gains rather than vague exhortations.
AI-written summary · about
chapters (13)
- 0:00Green software introduction
- 4:46Green Software Foundation
- 7:16Data center energy efficiency
- 10:26CPU usage energy impact
- 12:17Hardware efficiency and carbon
- 14:46Extending server lifetime
- 16:38Scaling out vs scaling up
- 19:32Carbon awareness and energy mix
- 23:33Space shifting workloads
- 26:06Time shifting workloads
- 29:05Avoiding emissions over offsets
- 31:12Measuring carbon footprint
- 35:35Green software summary
related talks
37mGreen Must Be Convenient
41mWriting Greener Software Even When You Are Stuck On-Prem
16mGreen Code: Transforming DevOps for a Sustainable Future
44mCloud computing and carbon emissions
17mJavaScript Saves the World
23mDriving cost-effective solutions to reduce carbon footprints
25mBuilding a Sustainable Future
44mTidy Space, Tidy Mind; How to Better Manage SQL Environments Across Cloud Providers