What Is a Larger GitHub Runner? More Cores, Higher Price
A larger GitHub runner is a hosted runner with more vCPU, memory, and disk than the default 2-core machine - faster for heavy jobs, but billed at a steep per-minute premium.
The standard GitHub-hosted Linux runner is modest (commonly 2 vCPU / 7 GB). For compile-heavy or memory-hungry jobs that is too small, so GitHub offers larger runners. They are faster - and a lot more expensive per minute.
What "larger" means
Larger runners come in sizes up to many vCPUs and tens of gigabytes of RAM, with more disk. You assign them via labels or runner groups and target them from runs-on for the jobs that need the horsepower.
When you need one
- Compile-heavy builds (C++, Rust, large monorepos) that saturate 2 cores.
- Memory-hungry jobs that OOM-kill on the standard size.
- Jobs where wall-clock feedback time justifies paying for speed.
The cost premium
Larger runners are billed at a multiple of the standard per-minute rate, scaling with size. A 16-core runner costs roughly eight times a 2-core one per minute, so a faster job is not automatically a cheaper job.
The managed comparison
Managed providers offer the same large sizes, usually well below GitHub's larger-runner pricing. Latchkey offers larger runner sizes typically around 69% cheaper than GitHub-hosted, so you can scale up CPU without the premium sting.
Faster is not always cheaper
Doubling cores roughly doubles the per-minute rate, so a bigger runner only saves money if the job actually gets proportionally faster. Compile-bound, parallelizable work benefits; a single-threaded job on a big runner just burns premium minutes.
Key takeaways
- A larger GitHub runner has more vCPU, memory, and disk than the default.
- It speeds up compile-heavy and memory-hungry jobs.
- It is billed at a steep multiple of the standard per-minute rate.
- Managed runners offer the same sizes at lower cost.