Tech Tip #26: Make the saving stick

Cheaper computing can mean more computing.

Video created by explainapaper.com

The problem

Efficiency makes computing cheaper, and cheaper computing invites more use. Without a limit, the saving is spent on more load and emissions don't fall: the rebound effect.

The fix you can use today

  • Pair efficiency work with an energy or carbon budget.
  • Retire the capacity an optimisation frees up.
  • Report absolute energy, not only efficiency per unit.

Researchers led by Lancaster University, with Mike Berners-Lee, argue that savings only count when total use is capped. GreenCode's climate case builds on this work.

Tools that help

  • Software Carbon Intensity (SCI) (Green Software Foundation): the Green Software Foundation's method, SCI = ((E x I) + M) per R, adopted as ISO/IEC 21031:2024
  • Cloud Carbon Footprint: estimates the energy and emissions of AWS, Azure and Google Cloud usage from billing and usage data

How GreenCode helps

GreenCode helps tackle this by measuring reductions in absolute terms, not only per task. Its climate case shows owners where capacity can be retired, so a saving can be banked rather than spent. More on this.

Tags

#governance#esg#cost

Sources

Transcript

Cheaper computing can mean more computing. Efficiency makes each task cheaper to run. And cheaper computing invites more use. Without a limit, the saving is spent on more load. Total emissions do not fall. This is called the rebound effect. Here is the fix you can use today. Pair every efficiency project with an energy or carbon budget. Retire the servers and capacity that an optimisation frees up. Report total energy, not only energy per task. Researchers led by Lancaster University worked on this with Mike Berners-Lee. They argue that savings only count when total use is capped. GreenCode's climate case builds on this work. The Software Carbon Intensity method scores carbon per unit of work. Add the totals from your cloud bills, using tools like Cloud Carbon Footprint. GreenCode helps tackle this by measuring cuts in total, not only per task. It shows where freed capacity can be retired, so the saving is banked. That was GreenCode Tech Tip number twenty-six. Follow for the next tip, and find more on greencode.ai/tech-tips.

All GreenCode Tech Tips · All GreenCode videos

  • Tip #26
  • For CTOs and technical leads
  • Length 1:09
  • Category Strategy, reporting and procurement
GreenCode

Want this checked on your own system? Talk to the GreenCode team.

Get in touch