How to Choose Between Standard and Larger GitHub Runners

The default GitHub-hosted Linux runner is 2 vCPU / 7 GB RAM; larger runners scale to 4, 8, 16, 32, and 64 vCPU with proportionally more memory and cost.

A standard runner is fine for most build and test jobs. Larger runners help CPU-bound or memory-hungry work, but they bill at a higher per-minute rate, so a bigger runner only pays off when it cuts wall-clock time enough to matter.

Runner sizes at a glance

Selecting a larger runner

jobs:
  build:
    # larger runners are configured in org/repo settings, then referenced by label
    runs-on: ubuntu-latest-8-cores
    steps:
      - uses: actions/checkout@v4
      - run: cargo build --release

When bigger is not better

Larger runners bill roughly linearly with vCPU, so an 8-core runner costs about 4x the standard rate. If your job is I/O bound or single-threaded, more cores sit idle and you pay more for the same duration. Benchmark before committing.

Related guides