RunsOn i7i.xlarge · local NVMe vs Namespace 4x16 x64
RunsOn does each build for 2.9–3.0× less; Namespace is 1.7–2.0× faster. Both 4 vCPU x64.
All three builds 3.0× cheaper on RunsOn: $0.0301 vs $0.0900Namespace 1.9× faster: 7m 02s vs 13m 25s
Rust build 2.9× cheaper on RunsOn: $0.0069 vs $0.0198Namespace 1.9× faster: 1m 33s vs 2m 54s
TypeScript build 2.9× cheaper on RunsOn: $0.0036 vs $0.0106Namespace 1.7× faster: 45s vs 1m 17s
Docker build 3.0× cheaper on RunsOn: $0.0196 vs $0.0596Namespace 2.0× faster: 4m 44s vs 9m 15s
RunsOn i7i.xlarge · local NVMe
jobs ran from Amazon.com (US)
Namespace 4x16
jobs ran from Namespace Labs (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 | Namespace | Gap |
|---|---|---|---|
| Cost | |||
| Cost per Rust build | $0.0069 | $0.0198 | 2.9× RunsOn |
| Cost per TypeScript build | $0.0036 | $0.0106 | 2.9× RunsOn |
| Cost per Docker build | $0.0196 | $0.0596 | 3.0× RunsOn |
| Price per minute | $0.0018 | $0.0120 overage rate | 6.6× RunsOn |
| Real builds, wall time | |||
| Rust build (spotify-player) | 2m 54s | 1m 33s | 1.9× Namespace |
| TypeScript build (opencode) | 1m 17s | 45s | 1.7× Namespace |
| Docker build (PostHog) | 9m 15s | 4m 44s | 2.0× Namespace |
| CPU & memory | |||
| PassMark single-thread (points) | 3,124 | 4,628 | 1.5× Namespace |
| PassMark CPU Mark, all cores (points) | 7,781 | 15,965 | 2.1× Namespace |
| sysbench CPU, 1 thread (events/s) | 2,984 | 6,887 | 2.3× Namespace |
| 7-Zip compression (MIPS) | 23,853 | 33,572 | 1.4× Namespace |
| Memory read bandwidth | 21.7 GiB/s | 44.7 GiB/s | 2.1× Namespace |
| Measurement | RunsOn | Namespace | Gap |
|---|---|---|---|
| Workspace disk (fio) | |||
| Random read, 4k QD32 (IOPS) | 150,053 | 1,202,685 | 8.0× Namespace |
| Random write, 4k QD32 (IOPS) | 82,487 | 564,373 | 6.8× Namespace |
| Random read, 4k QD1 (IOPS) | 11,192 | 104,443 | 9.3× Namespace |
| QD1 read latency, p99 | 281 µs | 11 µs | 26.0× Namespace |
| Sequential read | 1,010 MiB/s | 5.0 GiB/s | 5.0× Namespace |
| Sequential write | 788 MiB/s | 3.4 GiB/s | 4.4× Namespace |
| Sync write, 4k + fdatasync (IOPS) | 12,431 | 28,561 | 2.3× Namespace |
| Network, cache & Docker | |||
| Download from GitHub | 198 MiB/s | 187 MiB/s | 1.1× RunsOn |
| Cache restore, 4 GB (actions/cache) | 10s | 21s | 2.2× RunsOn |
| Cache save, 4 GB (actions/cache) | 9s | 13s | 1.5× RunsOn |
| docker pull | 5.9s | 3.2s | 1.8× Namespace |
| Database | |||
| pgbench read/write (TPS) | 7,158 | 13,662 | 1.9× Namespace |
| pgbench read-only (TPS) | 58,303 | 114,631 | 2.0× Namespace |
| Queue | |||
| Queue under burst load | 19s | 10s | 1.9× Namespace |
- ≈ 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