RunsOn m8a.xlarge · EBS gp3 vs Namespace 4x16 x64
RunsOn does each build for 3.7–5.8× less; on time, Namespace is faster on the Rust and Docker builds and neither is clearly faster on the TypeScript build. Both 4 vCPU x64.
All three builds 4.1× cheaper on RunsOn: $0.0218 vs $0.0900Namespace 1.7× faster: 7m 02s vs 12m 00s
Rust build 5.8× cheaper on RunsOn: $0.0034 vs $0.0198Namespace 1.2× faster: 1m 33s vs 1m 49s
TypeScript build 5.1× cheaper on RunsOn: $0.0021 vs $0.0106within run-to-run spread: 1m 03s · 45s
Docker build 3.7× cheaper on RunsOn: $0.0162 vs $0.0596Namespace 1.9× faster: 4m 44s vs 9m 08s
RunsOn m8a.xlarge · EBS gp3
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.0034 | $0.0198 | 5.8× RunsOn |
| Cost per TypeScript build | $0.0021 | $0.0106 | 5.1× RunsOn |
| Cost per Docker build | $0.0162 | $0.0596 | 3.7× RunsOn |
| Price per minute | $0.0013 | $0.0120 overage rate | 9.2× RunsOn |
| Real builds, wall time | |||
| Rust build (spotify-player) | 1m 49s | 1m 33s | 1.2× Namespace |
| TypeScript build (opencode) | 1m 03s | 45s | ≈ even |
| Docker build (PostHog) | 9m 08s | 4m 44s | 1.9× Namespace |
| CPU & memory | |||
| PassMark single-thread (points) | 3,809 | 4,628 | 1.2× Namespace |
| PassMark CPU Mark, all cores (points) | 13,481 | 15,965 | 1.2× Namespace |
| sysbench CPU, 1 thread (events/s) | 5,012 | 6,887 | 1.4× Namespace |
| 7-Zip compression (MIPS) | 38,485 | 33,572 | 1.1× RunsOn |
| Memory read bandwidth | 36.6 GiB/s | 44.7 GiB/s | 1.2× Namespace |
| Measurement | RunsOn | Namespace | Gap |
|---|---|---|---|
| Workspace disk (fio) | |||
| Random read, 4k QD32 (IOPS) | 2,994 | 1,202,685 | 401.7× Namespace |
| Random write, 4k QD32 (IOPS) | 2,991 | 564,373 | 188.7× Namespace |
| Random read, 4k QD1 (IOPS) | 1,825 | 104,443 | 57.2× Namespace |
| QD1 read latency, p99 | 807 µs | 11 µs | 74.7× Namespace |
| Sequential read | 401 MiB/s | 5.0 GiB/s | 12.7× Namespace |
| Sequential write | 401 MiB/s | 3.4 GiB/s | 8.6× Namespace |
| Sync write, 4k + fdatasync (IOPS) | 540 | 28,561 | 52.9× Namespace |
| Network, cache & Docker | |||
| Download from GitHub | 159 MiB/s | 187 MiB/s | 1.2× Namespace |
| Cache restore, 4 GB (actions/cache) | 16s | 21s | 1.3× RunsOn |
| Cache save, 4 GB (actions/cache) | 16s | 13s | 1.2× Namespace |
| docker pull | 4.8s | 3.2s | 1.5× Namespace |
| Database | |||
| pgbench read/write (TPS) | 3,256 | 13,662 | 4.2× Namespace |
| pgbench read-only (TPS) | 142,376 | 114,631 | 1.2× RunsOn |
| Queue | |||
| Queue under burst load | 17s | 10s | 1.7× 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); 9 of its jobs fell back to on-demand (AWS had no spot capacity for the type) and are priced at the spot rate over the same billed time
- Cost: a managed SaaS runner against RunsOn self-hosted on your AWS account; the effort of running it was not measured