CI Bench

Head to head · CI Bench v1

RunsOn vs GitHub-hosted larger runner (4 vCPU)

GitHub-hosted larger runner (4 vCPU) ran jobs 1.3× faster than RunsOn (95% interval 1.3× to 1.3×); RunsOn cost 91% less per job (at 100,000 jobs a month).

Self-hosted options spread fixed monthly costs over the monthly volume, so their cost per job changes with it; see the volume table.

Speed

× faster than GitHub-hosted (ubuntu-latest) · higher is better
RunsOn
1.2×
GitHub-hosted larger runner (4 vCPU)
1.6×
GitHub-hosted (ubuntu-latest)
1.0×

Cost per job

USD per $1.00 spent on GitHub-hosted (ubuntu-latest), at 100,000 jobs a month · lower is better
RunsOn
$0.12
GitHub-hosted larger runner (4 vCPU)
$1.39
GitHub-hosted (ubuntu-latest)
$1.00

Workload by workload

RunsOn had the lowest median time of the two on 3 of 12 workloads, GitHub-hosted larger runner (4 vCPU) on 9.
WorkloadRunsOnGitHub-hosted larger runner (4 vCPU)Lowest median
Burst: 20 jobs at once177 s154 sGitHub-hosted larger runner (4 vCPU)
cli327 s192 sGitHub-hosted larger runner (4 vCPU)
codex-lint623 s476 sGitHub-hosted larger runner (4 vCPU)
container174 s185 sRunsOn
fd89 s66 sGitHub-hosted larger runner (4 vCPU)
flask38 s21 sGitHub-hosted larger runner (4 vCPU)
guava897 s946 sRunsOn
monorepo288 s220 sGitHub-hosted larger runner (4 vCPU)
pydantic147 s154 sRunsOn
ts570 s435 sGitHub-hosted larger runner (4 vCPU)
vite437 s288 sGitHub-hosted larger runner (4 vCPU)
vue101 s67 sGitHub-hosted larger runner (4 vCPU)

Cost by volume

Mean cost per job in USD, from the benchmark’s sensitivity results
VolumeRunsOnGitHub-hosted larger runner (4 vCPU)
100,000 jobs a month$0.121$1.387
10,000 jobs a month$0.250$1.387
1,000 jobs a month$1.431$1.387

Failed runs

Counted, never replaced
RunsOn
1 of 360 measured runs (0.3%)
GitHub-hosted larger runner (4 vCPU)
3 of 360 measured runs (0.8%)

Each configuration page lists where its failures happened. All losses.

All results for this pair

One line per configuration pairing, generated from the benchmark data