RunsOn m8id.xlarge · local NVMe vs Namespace 4x16 x64
RunsOn does each build for 2.7–3.0× less; Namespace is 1.8–2.0× faster. Both 4 vCPU x64.
All three builds 2.9× cheaper on RunsOn: $0.0316 vs $0.0900Namespace 1.9× faster: 7m 02s vs 13m 19s
Rust build 2.7× cheaper on RunsOn: $0.0074 vs $0.0198Namespace 1.8× faster: 1m 33s vs 2m 44s
TypeScript build 3.0× cheaper on RunsOn: $0.0035 vs $0.0106Namespace 1.8× faster: 45s vs 1m 20s
Docker build 2.9× cheaper on RunsOn: $0.0206 vs $0.0596Namespace 2.0× faster: 4m 44s vs 9m 15s
RunsOn m8id.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.0074 | $0.0198 | 2.7× RunsOn |
| Cost per TypeScript build | $0.0035 | $0.0106 | 3.0× RunsOn |
| Cost per Docker build | $0.0206 | $0.0596 | 2.9× RunsOn |
| Price per minute | $0.0016 | $0.0120 overage rate | 7.3× RunsOn |
| Real builds, wall time | |||
| Rust build (spotify-player) | 2m 44s | 1m 33s | 1.8× Namespace |
| TypeScript build (opencode) | 1m 20s | 45s | 1.8× Namespace |
| Docker build (PostHog) | 9m 15s | 4m 44s | 2.0× Namespace |
| CPU & memory | |||
| PassMark single-thread (points) | 3,264 | 4,628 | 1.4× Namespace |
| PassMark CPU Mark, all cores (points) | 8,033 | 15,965 | 2.0× Namespace |
| sysbench CPU, 1 thread (events/s) | 3,079 | 6,887 | 2.2× Namespace |
| 7-Zip compression (MIPS) | 24,076 | 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) | 67,090 | 1,202,685 | 17.9× Namespace |
| Random write, 4k QD32 (IOPS) | 33,526 | 564,373 | 16.8× Namespace |
| Random read, 4k QD1 (IOPS) | 10,866 | 104,443 | 9.6× Namespace |
| QD1 read latency, p99 | 249 µs | 11 µs | 23.0× Namespace |
| Sequential read | 451 MiB/s | 5.0 GiB/s | 11.3× Namespace |
| Sequential write | 216 MiB/s | 3.4 GiB/s | 16.0× Namespace |
| Sync write, 4k + fdatasync (IOPS) | 7,903 | 28,561 | 3.6× Namespace |
| Network, cache & Docker | |||
| Download from GitHub | 187 MiB/s | 187 MiB/s | ≈ even |
| Cache restore, 4 GB (actions/cache) | 30s | 21s | 1.5× Namespace |
| Cache save, 4 GB (actions/cache) | 24s | 13s | 1.8× Namespace |
| docker pull | 5.7s | 3.2s | 1.8× Namespace |
| Database | |||
| pgbench read/write (TPS) | 7,066 | 13,662 | 1.9× Namespace |
| pgbench read-only (TPS) | 60,641 | 114,631 | 1.9× 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); 5 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