GitHub runner benchmark.
520 of 521 jobs finished across every suite, 1 failed (TypeScript).
- TypeScript is borderline at 8 GB or less: GitHub's 2 vCPU ran out of memory, on some runs only; Blacksmith and Warpbuild never ran out; Namespace, RunsOn and Ubicloud ran out on some runs; AWS CodeBuild ran out too; 16 GB passes everywhere.
- Measured swap at 8 GB or less: Blacksmith 2 vCPU has 11 GiB, GitHub 2 vCPU 3 GiB, RunsOn 2 vCPU 7.6 GiB, Ubicloud 2 vCPU 4 GiB and Warpbuild 2 vCPU 4 GiB; AWS CodeBuild 4 vCPU and Namespace 2 vCPU have none.
Fastest variant per build, any size
Fastest variant per build, any size
Variants
Fastest firstCheapest first; × against GitHub's fastest variant with 3 runs; cost per build, on the whole job's time.
Bar shades, light to dark, in execution order: setup = checkout + packages + toolchaincargo fmtcargo testclippy
Bar shades, light to dark, in execution order: toolchainclonebun installtypecheck
Bar shades, light to dark, in execution order: fetch sourcebuildx setupdocker build
Fixed costs not in cost per build
- GitHub Free $0/user/month2,000 Actions minutes a month on standard runners
- GitHub Team $4/user/month3,000 Actions minutes a month on standard runners
- GitHub Enterprise Cloud $21/user/month50,000 Actions minutes a month on standard runners
Every runner here needs a GitHub plan, so its per-user fee is not a cost of GitHub's own runners.
Standard runners are free in public repositories. Larger runners use no included minutes and are billed in public repositories too. Checked 2026-09-30
Over timeone point per run · since Sep 30
Loading every run…