RunsOn i7i.xlarge · local NVMe vs GitHub 4-core x64
RunsOn does each build for 6.6–8.9× less; on time, RunsOn is faster on the TypeScript build and neither is clearly faster on the Rust and Docker builds. Both 4 vCPU x64.
All three builds 8.2× cheaper on RunsOn: $0.0301 vs $0.2461RunsOn 1.3× faster: 13m 25s vs 17m 52s
Rust build 6.6× cheaper on RunsOn: $0.0069 vs $0.0457within run-to-run spread: 2m 54s · 3m 38s
TypeScript build 7.2× cheaper on RunsOn: $0.0036 vs $0.0258RunsOn 1.4× faster: 1m 17s vs 1m 44s
Docker build 8.9× cheaper on RunsOn: $0.0196 vs $0.1746within run-to-run spread: 9m 15s · 12m 30s
RunsOn i7i.xlarge · local NVMe
jobs ran from Amazon.com (US)
GitHub 4-core
jobs ran from Microsoft (US)
Side by side
Every measurement both runners share, cost first. The dot marks the better value; gap is the larger over the smaller.
| Measurement | RunsOn | GitHub | Gap |
|---|---|---|---|
| Cost | |||
| Cost per Rust build | $0.0069 | $0.0457 | 6.6× RunsOn |
| Cost per TypeScript build | $0.0036 | $0.0258 | 7.2× RunsOn |
| Cost per Docker build | $0.0196 | $0.1746 | 8.9× RunsOn |
| Price per minute | $0.0018 | $0.0120 | 6.6× RunsOn |
| Real builds, wall time | |||
| Rust build (spotify-player) | 2m 54s | 3m 38s | ≈ even |
| TypeScript build (opencode) | 1m 17s | 1m 44s | 1.4× RunsOn |
| Docker build (PostHog) | 9m 15s | 12m 30s | ≈ even |
| CPU & memory | |||
| PassMark single-thread (points) | 3,124 | 2,895 | 1.1× RunsOn |
| PassMark CPU Mark, all cores (points) | 7,781 | 7,511 | ≈ even |
| sysbench CPU, 1 thread (events/s) | 2,984 | 4,076 | 1.4× GitHub |
| 7-Zip compression (MIPS) | 23,853 | 18,743 | 1.3× RunsOn |
| Memory read bandwidth | 21.7 GiB/s | 24.1 GiB/s | 1.1× GitHub |
| Measurement | RunsOn | GitHub | Gap |
|---|---|---|---|
| Workspace disk (fio) | |||
| Random read, 4k QD32 (IOPS) | 150,053 | 19,575 | 7.7× RunsOn |
| Random write, 4k QD32 (IOPS) | 82,487 | 11,216 | 7.4× RunsOn |
| Random read, 4k QD1 (IOPS) | 11,192 | 7,286 | 1.5× RunsOn |
| QD1 read latency, p99 | 281 µs | 241 µs | 1.2× GitHub |
| Sequential read | 1,010 MiB/s | 394 MiB/s | 2.6× RunsOn |
| Sequential write | 788 MiB/s | 244 MiB/s | 3.2× RunsOn |
| Sync write, 4k + fdatasync (IOPS) | 12,431 | 4,163 | 3.0× RunsOn |
| Network, cache & Docker | |||
| Download from GitHub | 198 MiB/s | 95 MiB/s | 2.1× RunsOn |
| Cache restore, 4 GB (actions/cache) | 10s | 41s | 4.3× RunsOn |
| Cache save, 4 GB (actions/cache) | 9s | 34s | 4.0× RunsOn |
| docker pull | 5.9s | 16.4s | 2.8× RunsOn |
| Database | |||
| pgbench read/write (TPS) | 7,158 | 4,414 | 1.6× RunsOn |
| pgbench read-only (TPS) | 58,303 | 40,172 | 1.5× RunsOn |
| Queue | |||
| Queue under burst load | 19s | 3s | 6.3× GitHub |
- ≈ even: under 5% apart, or a build inside both runners' run-to-run spread
- Queue: identical jobs queued at the same instant (burst suite)
- RunsOn at EC2 spot, its default (7-day average of the cheapest us-east-1 zone's spot price, fetched 16 Nov 2026); its jobs ran on spot
- Cost: a managed SaaS runner against RunsOn self-hosted on your AWS account; the effort of running it was not measured