Open benchmarks for GitHub Actions runners. Real builds of public projects, pinned to a commit, run on a schedule. Every workflow, script and raw result is in this repository.
How fast each provider runs each suite, compared with GitHub-hosted runners (1.0×). Higher is faster.
| Suite | Workload |
|---|---|
| Rust | Cold cargo test and clippy of spotify-player |
| Node | Cold bun install and typecheck of opencode |
| Docker | docker buildx build of PostHog's production image, no cache |
| Cache | Save and restore a 4 GiB file with actions/cache |
All runners have 4 vCPU (x64). Celesto results come from this repository's runner suites. Other providers' results come from the runs-on.com public benchmark data, which uses the same workloads and settings. Updated daily.
Full results: time per phase and hardware →
| Benchmark | What it measures | Guide |
|---|---|---|
| Runner suites | Rust, Node and Docker builds, a 4 GiB cache, hardware tests and a burst of 15 jobs | docs/suites.md |
| Matched CPU and cache | CPU throughput and a 512 MiB cache on GitHub-hosted and Celesto side by side (Nov 2 results) | docs/matched.md |
| Docker | Image builds, layer caches, and a Python API with PostgreSQL (Oct 17 results) | docker-bench/README.md |
- Fork this repository and enable Actions in the fork.
- Install the Celesto CI app on the fork, with a workspace that has credit for the Large runner.
- Open Actions, pick a workflow, and click Run workflow.
To test another runner, change runs-on in the workflow. docs/suites.md explains the rest.