Benchmarks
There are no benchmark numbers on this site yet. We publish a number only after our own harness has measured it on the machines we sell. Until then, every claim about raw.computer is about what it does, not how fast it does it.
What we will measure
| Measurement | From | To |
|---|---|---|
| Time to ready | POST /v1/sandboxes sent |
a command in the new sandbox answers |
| Time to fork | fork requested | a command in the fork answers |
| Snapshot time | snapshot requested | the snapshot is usable |
| Exec round trip | a command is sent to a running sandbox | its exit code is back |
| CPU | single-core and all-core scores inside a sandbox of each class | |
| Disk | fsync latency (p50, p99) and random-write IOPS inside a sandbox |
|
| A real CI job | a reference repository's test suite, start to finish |
How
- Each measurement is repeated many times and reported as p50, p95 and p99, never as a best run.
- Runs happen at different hours, from a client in the same region as the cell, and say which region and when.
- Every number is published with the harness version, the raw results and the date it was measured.
- Comparisons with other providers use the same harness, the same size and the provider's public list price, on the same days.
- A number that a newer run no longer reproduces is replaced, and the change is dated.
Until then
The pricing and limits pages are exact today. Speed numbers will appear on this page when they are measured.