Enhance Software Quality Testing to be CO2 aware
summary
Proposal to schedule high-energy test runs when grid carbon intensity is low using Electricity Maps (and WattTime) APIs that return carbon intensity (gCO2/kWh) and 24-hour forecasts; example shows a low/usable window versus a peak of 337 gCO2/kWh. Practical endpoints include current intensity, production/consumption breakdowns and a forecast endpoint; client libraries and curl/JS/Python snippets exist and a disable_estimations=true parameter forces forecasted-only behavior. Use-case: trigger stress or regression suites in chosen region at forecasted low-carbon slots.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 0:22Agenda and key concepts
- 1:29Types of tests in SQE
- 4:22Carbon emissions and clean electricity
- 5:24Carbon aware software
- 6:49Electricity Maps API
- 9:46Carbon aware testing automation
- 11:18Q&A
related talks
43mGreen Software – How To Make Our Applications Carbon Aware?
35mGreen Software Principles and Embedding Carbon Awareness in Your Applications
41mWriting Greener Software Even When You Are Stuck On-Prem
31mTrack your code's CO2 emissions with Code Carbon
44mCloud computing and carbon emissions
14mSLOs, SREs, and GHGs
45mLaying the Foundation on OSS Environmental Sustainability
50mResponsible computing: how about a survey of measurement tools?