High performance sandbox benchmarks

Choose a statistic (min, p50, p95, or max), then a real-world pipeline or synthetic benchmark. Bars rank providers best-first against the leader. Hover or focus a row for instance metadata and the raw sample distribution; select it to jump to that metric in the table below.

Each row shows the single metric with that provider's widest total (min-max) spread, ranked by IDR (p10-p90). The distribution is every trial the run recorded for that metric, pooled across the provider's replicate sandboxes. Phoronix repeats a benchmark several times inside each sandbox, and all of those measurements count, so a row's n is trials rather than sandboxes. Convergence-mode suites repeat until Phoronix settles, which means a noisy sandbox contributes more trials than a quiet one and weighs on the interval accordingly. Metrics that depend on the public Internet, including WAN iperf, repository cloning, and dependency installation, are excluded so the figure reflects sandbox precision; local networking such as iperf loopback remains eligible. The suite and metric vary by provider and are named on every row. Because the units are unlike, every interval is given as a percentage of its own metric's p50. Dots are individual trials and the vertical line marks p50; select Total, IQR, or IDR to highlight and read that range, or hover a row for its numerical endpoints.

Every environment ran the same harness against freshly created sandboxes targeting 4 vCPU · 8 GB RAM · 40 GB disk. Synthetic suites ran on 3 replicate sandboxes each, repeating passes until Phoronix's own convergence criterion was met, so pass counts vary by how noisy the sandbox was; each real repository pipeline (Better Auth, Mastra, and OpenClaw) ran cold on 12 fresh sandboxes, through that repository's own CI tasks. Every figure is a median (p50) pooled across an environment's sandboxes, and every cell keeps the individual trials behind that median, which is what the Precision section reads.

Every catalogued metric this run emitted, labeled and grouped exactly as the dataset's own leaderboard labels it. Each cell shows the median and its ratio to the row's best; amber deepens the further a provider sits behind, teal marks the best. ↓ means lower is better; ∑ marks a value derived from other rows. Click a metric name to open it in the results explorer.

Specs, storage shape, hardware mixtures, and egress identity come directly from the run's embedded in-sandbox probes and Phoronix metadata. When replicate sandboxes reported different host CPU models, the CPU row shows the fleet count and the disclosure below lists every model. Environment flags mark an off-target resource, gVisor isolation, or a heterogeneous fleet; missing probe values remain blank rather than being filled from another run.

Only providers marked validated by the dataset render as comparison columns. Every skipped or failed suite record below comes from this run, including universally unrecorded tasks and provider-specific failures; no older run fills a missing cell. Providers attempted without any validated metrics are disclosed after the table instead of becoming empty comparison columns.