Phases Completed
Environment
Sandbox hardware and software context — use this to tell whether a provider is faster because of more CPUs/memory, not a faster disk or network.
Disk Usage
Total disk usage (du -sx) captured after each phase — a proxy for disk I/O and storage cost. Some providers report 0 here if their sandbox filesystem doesn't support usable disk-usage reporting.
Total Duration
Total Duration Over Time
Prepare
Prepare Over Time
Bun Download
Bun Download Over Time
Bun Unpack
Bun Unpack Over Time
Clone
Clone Over Time
Install
Install Over Time
Typecheck
Typecheck Over Time
Raw Iterations
Each iteration runs the full clone + install + typecheck cycle from a fresh sandbox.
| # | Phases | Total | Prepare | Bun DL | Bun Unpack | Clone | Install | Typecheck | Error |
|---|---|---|---|---|---|---|---|---|---|
| 1 | 7/7 | 110.02s | 2.27s | 0.37s | 0.70s | 2.22s | 14.16s | 85.56s | — |
Methodology
What We Measure
Each run executes a cold clone + install + typecheck cycle of the opencode repository inside a fresh sandbox: install system packages and Node.js, download and unpack Bun, shallow-clone opencode at a pinned commit, run bun install, then bun typecheck.
Each provider runs 1 iteration per scheduled benchmark run. Benchmarks run via GitHub Actions and results are committed to the public benchmarks repo.
How We Score
The Composite Score is the median number of the 7 benchmark phases (prepare, cache clear, bun download, bun unpack, clone, install, typecheck) a provider completed before failing, if any — shown as a fraction like 7/7.
The other metrics (Total, Prepare, Clone, Install, Typecheck) are real-world phase durations in seconds — providers are ranked by median duration (lower is better) when one of those is selected. The benchmark requires curl, root/sudo, and a package manager (apt, dnf, or apk) inside the sandbox — providers without those capabilities fail early, which shows up as a low phase count.