Your GitHub Actions Bill Is Mostly Waiting: Measure Runner-Minutes Before You Optimise Anything
Every team that says "CI is expensive" eventually gets asked the follow-up question: how expensive, exactly — and where? Most can't answer it. So the optimisation work starts with folklore ("add caching"), burns a sprint, and ends with a bill that looks about the same. There is a cheaper order of operations: measure first, in one unit, ranked. The unit is runner-minutes per day, per workflow.…
Your GitHub Actions bill is largely contingent upon waiting, duplication, and unnecessary runs. Before optimizing, it's crucial to measure the runner-minutes per day for each workflow. The unit is measured by calculating the wall-clock time for each completed run, dividing it by the days covered, and summing it per workflow. Once the data is available, you can identify waste patterns, such as cold caches, redundant builds, oversized matrices, unused runs, frequent nightly rebuilds, and employing expensive runners for insignificant tasks. By addressing these issues in order, you can significantly reduce costs and improve efficiency.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.