Tech Tip #71: A software saving is worth more at the meter

Save 100 kWh in software, save up to 158 at the meter.

The problem

Software savings are counted at the server, but every kilowatt-hour of compute also needs cooling and power distribution. The less efficient the building, the more a software saving is worth.

The fix you can use today

  • Multiply server-level savings by your facility's PUE for an upper bound.
  • Ask your provider or facility for its PUE.
  • Use the figure when you make the business case for optimisation.

The Green Software Foundation explains that every unit saved in a server also saves cooling and power losses. GreenCode keeps advice like this in mind in its 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
  • ipmitool: reads a server's power from its management controller (`ipmitool dcmi power reading`)

How GreenCode helps

GreenCode helps tackle this by measuring reductions in absolute terms and showing owners where capacity can be retired, so a saving is banked rather than spent. More on this.

Tags

#data-centre#cost#esg

Sources

All GreenCode Tech Tips

  • Tip #71
  • For CTOs and technical leads
  • Category Strategy, reporting and procurement
  • Format short video
GreenCode

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

Get in touch