Co2 Emission Efficiency Of Software Platforms: Is There A Price For Sustainability?
summary
A published framework to estimate CO2 from software maps required hardware for a workload to embodied manufacturing emissions, component energy use, and grid carbon intensity, then sums device+operation emissions. Applied to a petabyte workload it produces 110 tons CO2/year per PB for Aerospike versus 670 tons CO2/year per PB for Cassandra using Ireland grid numbers, implying roughly a 500‑ton annual CO2 saving and lower running costs when efficiency reduces resource needs.
AI-written summary · about
chapters (7)
- 0:00Introduction and background
- 3:31Shift from efficiency to scalability
- 9:50IT industry’s growing CO2 emissions
- 12:24Efficiency and CO2 emissions framework
- 15:25Case study: Aerospike vs Cassandra
- 17:57Significance of CO2 savings
- 19:41Call to action for sustainability
related talks
59mReducing The Carbon Footprint Of Your Software Systems
14mSLOs, SREs, and GHGs
38mGreen software: How can tech contribute to worldwide sustainability effort?
34mCarbon Footprint–Aware Software Development
38mBetter Coding for the Climate?!
41mWriting Greener Software Even When You Are Stuck On-Prem
45mLaying the Foundation on OSS Environmental Sustainability
44mCloud computing and carbon emissions