Fastest GitHub Actions Runners
Comments on “Fastest GitHub Actions Runners”
Claim-checked. Scored by all three judges, and its checkable claims were compared with the sources it cites. How far stories are checked
A benchmark of 57 GitHub Actions runner configurations across nine providers, timing three builds and pricing each run. Namespace's 8-vCPU x86 runner finished all three builds in 5m 04s for $0.1444, while RunsOn's 8-vCPU m8a.2xlarge with tmpfs was nearly as fast at $0.0206.
Why it ranked
No. 25 of 137 with a score of 0.63. The panel rated it highest on new information (0.88) and practical relevance (0.85), lowest on significance (0.47). Placed No. 25, No. 45 by score alone: the fourth Infrastructure & DevOps story of the day (−0.020). The placement terms move stories; they are not part of the score.
- AI judgeJudge 2claude-haiku-5-5
- Benchmark comparing CI runner providers on build time and cost; practical for devops buyers, dense data table with vendor-sponsored links and some methodology caveats, though not a landmark.
- AI judgeJudge 3gpt-5.6-luna
- A detailed, reproducible comparison of 57 GitHub Actions runner configurations across speed, cost, storage, caching, and queue behavior. It is highly actionable for CI/platform decisions, though its scope is benchmarking rather than a field-changing development.
Each judge wrote its line after answering the rubric, with the site and the author still hidden. Every answer behind this is in the table under Score.
Score
0.63total under rubric v2.3
- Significance0.47
- Reader interest0.69
- Audience breadth0.57
- Practical relevance0.85
- Substantiated0.85
- Technical depth0.74
- New information0.88
- Counts against: Promotional0.12
- Counts against: Overclaim0.22
Each judge’s answer per question (0–1), their mean and spread, and what the question adds to the score (weight × mean).
| Question | Judge 1 | Judge 2 | Judge 3 | Mean | Spread | Weight | Contribution (weight times mean) |
|---|---|---|---|---|---|---|---|
| SignificanceHow much does this change what people in tech know or can do? | 0.52 | 0.30 | 0.58 | 0.47 | 0.28 | +0.24 | +0.112 |
| Reader interestWould a well-informed senior engineer or tech founder want to read this today, and likely pass it on? | 0.65 | 0.60 | 0.82 | 0.69 | 0.22 | +0.26 | +0.179 |
| Audience breadthHow many people who build technology does it concern? | 0.59 | 0.50 | 0.62 | 0.57 | 0.12 | +0.13 | +0.074 |
| Practical relevanceHow useful is it to someone who builds software or tech products? | 0.93 | 0.85 | 0.78 | 0.85 | 0.15 | +0.22 | +0.188 |
| SubstantiatedHow well is it backed? Consider whether it is the primary source, and whether its main claims come with data, code, a demo, a reproducible method or citations. | 0.94 | 0.70 | 0.90 | 0.85 | 0.24 | +0.05 | +0.042 |
| Technical depthHow technically substantive is it? | 0.87 | 0.65 | 0.70 | 0.74 | 0.22 | +0.05 | +0.037 |
| New informationDoes it contain information absent from the stories covered in the last 7 days (list provided)? | 0.83 | 0.85 | 0.97 | 0.88 | 0.14 | +0.05 | +0.044 |
| PromotionalIs it mainly marketing with little substance (a press release, ad or sponsored post with no real information)? A launch post that carries real news is not promotional. | 0.08 | 0.25 | 0.04 | 0.12 | 0.21 | −0.19 | −0.023 |
| OverclaimDo the headline or conclusions claim more than the body supports? | 0.28 | 0.30 | 0.08 | 0.22 | 0.22 | −0.11 | −0.024 |
| Sum of contributions | +0.628 | ||||||
| Claim-check penalty | 0.000 | ||||||
| Total, as published | 0.628 | ||||||
Spread is the highest minus the lowest judge answer. marks a spread above 0.40: the judges disagree, and the story is marked contested.
The badge for this ranking, for the author's page or anyone's: one line of HTML, and it links back here.
<a href="https://rubric.hrih.si/editions/2026-11-04/25/"><img src="https://rubric.hrih.si/badge/2026-11-04/25.svg" alt="Ranked #25 on Rubric, 4 Nov 2026" width="238" height="28"></a>Claim check
Claim check: 2 matches source · 2 no source given · 4 couldn’t check. Each claim is compared with the source the article itself cites; a flag is published only when both checkers agree.
Couldn’t checkFirst, only or fastest
Namespace 8x32 was the fastest runner, finishing all three builds in 5m 04s at a cost of $0.1444.
The source was unreachable, paywalled or too long, or the two checkers disagreed.
The article says “Fastest: Namespace 8x32, 5m 04s · $0.1444 for all three builds”
The source says No passage could be compared.
Source cited by the article: runs-on.com/benchmarks/runners/namespace
No source givenNumber
38 of 57 runners finished all three builds, and 19 do not run the Docker build on purpose.
The article gives no link or citation for it.
The article says “38 of 57 runners finished all three builds; 19 do not run the Docker build on purpose”
The source says No source to compare with.
Matches sourceBenchmark result
RunsOn m8a.2xlarge with tmpfs is a best trade-off runner, finishing all three builds in 5m 28s for $0.0206.
The cited source says the same thing.
The article says “RunsOn m8a.2xlarge · tmpfs5m 28s · $0.0206 for all three builds”
The source says “m8a.2xlarge · tmpfs 8 vCPU · 32 GB5 runs1m 15s, cost per build $0.0050$0.0137; phases: setup 14s, cargo test 37s, clippy 23s, ×1.34”
Source cited by the article: runs-on.com/benchmarks/runners/runson
Couldn’t checkBenchmark result
RunsOn r8a.xlarge with tmpfs is a best trade-off runner, finishing all three builds in 7m 38s for $0.0186.
The source was unreachable, paywalled or too long, or the two checkers disagreed.
The article says “RunsOn r8a.xlarge · tmpfs7m 38s · $0.0186 for all three builds”
The source says No passage could be compared.
Source cited by the article: runs-on.com/benchmarks/runners/runson
Couldn’t checkBenchmark result
Namespace 8x16 is a best trade-off runner, finishing all three builds in 5m 14s for $0.0690.
The source was unreachable, paywalled or too long, or the two checkers disagreed.
The article says “Namespace 8x165m 14s · $0.0690 for all three builds”
The source says No passage could be compared.
Source cited by the article: runs-on.com/benchmarks/runners/namespace
Couldn’t checkBenchmark result
GitHub 8-core finished all three builds in 10m 32s at $0.2966, much slower and costlier than the top runners.
The source was unreachable, paywalled or too long, or the two checkers disagreed.
The article says “GitHub 8-core 8 vCPU 32 GB VM disk Xeon 6973P-C +4 $0.2966 10m 32s”
The source says No passage could be compared.
Source cited by the article: runs-on.com/benchmarks/runners/github
Matches sourceBenchmark result
AWS CodeBuild large finished all three builds in 15m 12s at a cost of $0.3417.
The cited source says the same thing.
The article says “AWS CodeBuild large 8 vCPU 16 GB EBS Xeon 8488C +2 $0.3417 15m 12s”
The source says “large 8 vCPU · 16 GBEBS · 5 runs2m 12s, cost per build $0.0493”
Source cited by the article: runs-on.com/benchmarks/runners/aws-codebuild
No source givenNumber
Cost per build is calculated as job duration times list price per minute, using seconds as run and never rounded up to a billing increment.
The article gives no link or citation for it.
The article says “Cost per build: job duration × list price per minute, seconds as they ran, never rounded up to a billing increment”
The source says No source to compare with.
Also covered by
No other coverage was clustered with this story.
Elsewhere
Elsewhere: HN 2 pts, not on front page
Recorded for context only, checked 4 Nov 2026, 05:47 UTC. It played no part in the ranking.