Published studies put cloud servers active only 10 to 30% of the time, yet an idle machine still draws a significant fraction of its peak power. Servers are bought for the busiest moment, and slow software makes that moment bigger than it needs to be.
The fix you can use today
First cut the load: fix the wasteful code so each request needs less.
Then right-size: fewer or smaller machines for what is left.
Let quiet services scale to zero, and look for machines idle all day.
Studies reviewed by GreenCode researchers found that many cloud servers are busy only 10 to 30% of the time. GreenCode's research review draws on this work.
Tools that help
GreenCode Constitution skill (GreenCode researchers): open-source energy principles and a catalogue of 37 energy anti-patterns that an AI coding agent can follow to find and fix waste like this
Scaphandre: measures the power drawn by each process on a Linux server and exports it to Prometheus and other monitoring stacks
Kepler: exports energy estimates per pod and container on Kubernetes, using eBPF and hardware counters
How GreenCode helps
GreenCode helps tackle this by mapping a running estate and tracing its energy and CO2e to the services that cause it. That shows which services run hot and which are barely running at all. More on this.
