Benchmarks
Benchmark StarSling against GitHub-hosted runners on your own workflows
StarSling runners can deliver up to 6x faster build times compared to GitHub-hosted runners, depending on workload characteristics. The best way to see the difference is to benchmark your own workflows — the guide below shows how.
Real-World Results
What StarSling delivered for real teams after they switched runs-on — faster runners plus the optimizations StarSling agents shipped and the team merged:
| Repo | Metric | GitHub-hosted | StarSling | Improvement |
|---|---|---|---|---|
| Mastra | Slowest test suite | ~30m | ~5m | ~6x faster |
| Mastra | Job queue under load | ~15m | under 2m | ~8x shorter |
| Better Auth | E2E runtime per job | 2m 22s | 1m 04s | ~2x faster |
Across all its CI and E2E jobs, Better Auth saves roughly 20,000 CI minutes every month.
These are live customer results — each links to its case study with the full methodology and the agent-authored PRs behind the numbers.
Why StarSling is Faster
1. 30% Faster Hardware
| Spec | GitHub-hosted | StarSling |
|---|---|---|
| CPU | 4th Gen AMD EPYC* | 5th Gen AMD EPYC |
| Cores | 4 vCPU | 4 vCPU |
| Memory | 16 GB | 16 GB |
5th Gen AMD EPYC processors deliver ~30% better single-threaded performance over 4th Gen, directly improving build and test execution times.
* Not publicly disclosed by GitHub in their docs but inferred based on publicly available information.2. Unlimited Concurrency
No concurrency limits means every job gets a runner quicker, even during peak CI loads.
Run Your Own Benchmark
Compare your actual workflows side by side — run the same steps on a GitHub-hosted runner and a StarSling runner, then compare the timings:
jobs:
github-hosted:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- run: time npm ci && time npm run build
starsling:
runs-on: starsling-ubuntu-24.04
steps:
- uses: actions/checkout@v4
- run: time npm ci && time npm run build