kodebeat / papers / greenops
Linting for the energy a codebase wastes
A static analyser for energy-wasteful patterns.
Flags busy loops, sub-100ms polling, every-minute crons, SELECT *, full-history CI clones, peak-sized instances and missing resource limits, across source, CI config, Terraform, manifests and Dockerfiles. Every finding explains why the pattern wastes energy and carries an order-of-magnitude gCO2e steer from four published sources. For the team with a sustainability target and no idea which line to change first.
What is in it
- The problem — what goes unanswered without it, and who notices first.
- Why the obvious alternative falls short — stated plainly, including where it is the better choice.
- How it works — the method, not a feature list.
- Concrete use cases — with console output quoted from the repository, never reconstructed.
- The methodology behind any number it emits — every term shown, so the figure survives a question.
- What it deliberately does not do — the section most papers leave out.
Part of the GreenOps theme.
Get the PDF
One email with the download link, and this paper already selected. No follow-up sequence.