Speed
× faster than GitHub-hosted (ubuntu-latest) · higher is betterVitko Runners (warm starts + test splitting)
2.3×
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 betterVitko Runners (warm starts + test splitting)
$0.16
GitHub-hosted larger runner (4 vCPU)
$1.39
GitHub-hosted (ubuntu-latest)
$1.00
Workload by workload
Vitko Runners had the lowest median time of the two on 12 of 12 workloads, GitHub-hosted larger runner (4 vCPU) on 0.
Cost by volume
Mean cost per job in USD, from the benchmark’s sensitivity results
Failed runs
Counted, never replaced- Vitko Runners (warm starts + test splitting)
- 3 of 360 measured runs (0.8%)
- Vitko Runners
- 0 of 360 measured runs (0.0%)
- 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- Vitko Runners (warm starts + test splitting) ran jobs 1.5× faster than GitHub-hosted larger runner (4 vCPU) (95% interval 1.4× to 1.5×); Vitko Runners (warm starts + test splitting) cost 89% less per job (at 100,000 jobs a month).
- Vitko Runners ran jobs 1.1× faster than GitHub-hosted larger runner (4 vCPU) (95% interval 1.1× to 1.2×); Vitko Runners cost 89% less per job (at 100,000 jobs a month).