Guides
How to right-size your runners
Runner sizes were chosen once and never revisited.
5 min read
Runner sizes were chosen once and never revisited.
Why it happens
Without utilization data, teams pick a size defensively and never scale it back down.
How to fix it
- Collect CPU and memory utilization per job for two weeks
- Scale down anything below 40% average CPU utilization
- Scale up anything pinned at 100% that sits on the critical path
- Re-check quarterly — test suites grow and the right size moves
Your next build could be twice as fast, at half the price
Start free. Migrating away is the same one line, and we publish that diff too.
Related
How to reduce GitHub Actions costsThe CI bill grows faster than the team and nobody is sure why.How to measure CI cost per pull requestYou know the monthly total but not what a single pull request costs.How to attribute CI cost to teamsCI spend is one line on the invoice and no team feels responsible for it.How to set a CI minutes budgetSpend is discovered at the end of the month rather than controlled during it.