CI Bench

Head to head · CI Bench v1

Blacksmith vs GitHub-hosted (ubuntu-latest)

Blacksmith ran jobs 1.6× faster than GitHub-hosted runners (ubuntu-latest, 2 vCPU) (95% interval 1.3× to 1.7×); Blacksmith cost 52% less per job (at 100,000 jobs a month).

Speed

× faster than GitHub-hosted (ubuntu-latest) · higher is better
Blacksmith
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
Blacksmith
$0.48
GitHub-hosted (ubuntu-latest)
$1.00

Workload by workload

Blacksmith had the lowest median time of the two on 11 of 12 workloads, GitHub-hosted (ubuntu-latest) on 1.
WorkloadBlacksmithGitHub-hosted runners (ubuntu-latest, 2 vCPU)Lowest median
Burst: 20 jobs at once97 s259 sBlacksmith
cli286 s368 sBlacksmith
codex-lint448 s884 sBlacksmith
container386 s239 sGitHub-hosted runners (ubuntu-latest, 2 vCPU)
fd65 s92 sBlacksmith
flask22 s23 sBlacksmith
guava735 s1167 sBlacksmith
monorepo177 s384 sBlacksmith
pydantic103 s179 sBlacksmith
ts401 s784 sBlacksmith
vite360 s603 sBlacksmith
vue76 s121 sBlacksmith

Cost by volume

Mean cost per job in USD, from the benchmark’s sensitivity results
VolumeBlacksmithGitHub-hosted runners (ubuntu-latest, 2 vCPU)
100,000 jobs a month$0.482$1.000
10,000 jobs a month$0.482$1.000
1,000 jobs a month$0.482$1.000

Failed runs

Counted, never replaced
Blacksmith
3 of 360 measured runs (0.8%)
GitHub-hosted runners (ubuntu-latest, 2 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