Mastodon CI on GitHub Actions: build times and cost per run on GitHub vs Sengi runners (Nov 2026)
How long does Mastodon CI take on GitHub Actions, and what does a build cost?
Measured November 17, 2026 on Mastodon (mastodon/mastodon, commit 3987b9f): Docker image build (linux/amd64) after a one-file change, layer cache on. Results at 4 vCPU, GitHub-hosted 4 vCPU took 153 s median over 4 runs, $0.036 a build; Sengi Basic 4 vCPU took 168 s median over 3 runs, $0.006 a build, 10% more time and 83% less cost against GitHub-hosted 4 vCPU; Sengi Premium 4 vCPU had not enough runs (2 measured, 1 failed), so no median is printed. At 4 vCPU, Sengi Basic 4 vCPU took more time than GitHub-hosted 4 vCPU: 168 s against 153 s. Not like-for-like with GitHub’s 4 vCPU runner: Sengi Basic 2 vCPU took more time than GitHub-hosted 4 vCPU. Times are median job seconds, printed only with at least 3 runs; these results cover this build only. 2 Mastodon jobs failed and are not counted in any median: Sengi Basic 2 vCPU: Sengi's build cache served a truncated layer, a short read ending in unexpected EOF, so the Docker image build failed; Sengi Premium 4 vCPU: Sengi's build cache served a truncated layer, a short read ending in unexpected EOF, so the Docker image build failed.
Measured November 17, 2026, last checked November 17, 2026. This page shows one project from the 12-project benchmark. Every number is in one JSON file and a CSV file, and every median links to its run log in the public repository sengirunners/benchmarks.
Mastodon results at 4 vCPU: GitHub’s runner, Sengi Basic 4 vCPU and Sengi Premium 4 vCPU
One row per runner. Time is the median job run time in seconds, from the job’s start to its end, over the runs counted; min and max are the fastest and slowest of those runs. Cost per build is the median of the runs’ billed minutes, each job rounded up to a whole minute, at the runner’s list price. A cell with fewer than 3 runs prints “not enough runs”.
| Project | Commit | Runner | Runs | Median time (s) | Min–max (s) | Cost per build (USD) | Time against GitHub | Cost against GitHub |
|---|---|---|---|---|---|---|---|---|
| Mastodon | 3987b9f | GitHub-hosted 4 vCPU | 4 | 153 | 124–200 | $0.036 | baseline | baseline |
| Mastodon | 3987b9f | Sengi Basic 4 vCPU | 3 | 168 | 115–190 | $0.006 | 10% more time | 83% less cost |
| Mastodon | 3987b9f | Sengi Premium 4 vCPU | 2 (1 failed) | not enough runs | – | – | – | – |
Mastodon median job time at 4 vCPU
Not like-for-like: Sengi Basic 2 vCPU and Sengi Premium 2 vCPU
Sengi Basic 2 vCPU has half the cores of GitHub’s 4 vCPU runner. Sengi Premium 2 vCPU has half the cores of GitHub’s 4 vCPU runner. These Sengi runners were run on the same project; they are not a like-for-like comparison, and no GitHub runner of their size was measured. The last two columns still set each against GitHub-hosted 4 vCPU.
| Project | Commit | Runner | Runs | Median time (s) | Min–max (s) | Cost per build (USD) | Time against GitHub | Cost against GitHub |
|---|---|---|---|---|---|---|---|---|
| Mastodon | 3987b9f | Sengi Basic 2 vCPU | 3 (1 failed) | 208 | 138–1643 | $0.004 | 36% more time | 89% less cost |
| Mastodon | 3987b9f | Sengi Premium 2 vCPU | 4 | 129 | 127–159 | $0.009 | 16% less time | 75% less cost |
Where did Sengi take more time on Mastodon?
Every Mastodon result where a Sengi runner’s median was above GitHub’s is printed in the tables above and listed here.
At 4 vCPU, the same size as GitHub’s runner
- Mastodon, Sengi Basic 4 vCPU: 168 s against 153 s on GitHub’s runner, 10% more time, at $0.006 a build against $0.036.
Not like-for-like: smaller or larger Sengi runners against GitHub’s 4 vCPU runner
- Mastodon, Sengi Basic 2 vCPU: 208 s against 153 s on GitHub’s runner, 36% more time, at $0.004 a build against $0.036.
What was left out of the Mastodon medians?
2 Mastodon jobs failed and are not counted in any median: Sengi Basic 2 vCPU: Sengi's build cache served a truncated layer, a short read ending in unexpected EOF, so the Docker image build failed; Sengi Premium 4 vCPU: Sengi's build cache served a truncated layer, a short read ending in unexpected EOF, so the Docker image build failed. Each failed job is also counted in its row’s failures.
- Job 134048517537 on Sengi Basic 2 vCPU: Sengi's build cache served a truncated layer, a short read ending in unexpected EOF, so the Docker image build failed
- Job 134032483827 on Sengi Premium 4 vCPU: Sengi's build cache served a truncated layer, a short read ending in unexpected EOF, so the Docker image build failed
How was Mastodon measured?
- Time: Job run time, start to end, from the GitHub API. Queue time is kept apart.
- Runs: Median of the measured runs, with n, min and max; a median needs n >= 3.
- Cost: Billed minutes (each job rounded up to a whole minute) times the runner's list price per minute.
- GitHub cost: GitHub does not bill public repositories for this runner; its cost is what a private repository pays at GitHub's listed rate for the measured size.
- Order: One runner class at a time; at most four jobs at once within a run. One warm-up run per class first fills dependency caches.
- Selection: The project list is the whole workload list of an existing open-source CI benchmark suite, adopted before running it here. Each project is pinned to a release commit.
- Exclusions: Every run is listed. A job is left out of the medians only for the reason given next to it.
- Dates: 2026-11-17 to 2026-11-17.
- Runner size: the vCPU count printed for each runner was read with
nprocinside the job, not taken from a label. - Prices: GitHub-hosted 4 vCPU $0.012, Sengi Basic 2 vCPU $0.001, Sengi Premium 2 vCPU $0.003, Sengi Basic 4 vCPU $0.002 and Sengi Premium 4 vCPU $0.006 a minute. GitHub does not bill public repositories for its standard runner, which is 4 vCPU there. The GitHub column is priced at GitHub’s listed rate for its 4 vCPU Linux larger runner (sold to Team and Enterprise Cloud organizations), $0.012 a minute: what a private repository pays for these minutes beyond its plan’s included usage.
- Queue time is recorded for every run in the data files and is not part of the times above.
| Project | Repository | Language | What the job runs | Commit |
|---|---|---|---|---|
| Mastodon | mastodon/mastodon | Docker | Docker image build (linux/amd64) after a one-file change, layer cache on | 3987b9fd624010eeeaeb7cad96606b05aa813f6a |
The benchmark workflows are at commit e73c896795525a61b47ce9f44657a1a045b0a98b of sengirunners/benchmarks. Mastodon is not affiliated with Sengi; its name identifies the code that was built.
Other projects in the benchmark
The same measurement for the other 11 projects, and all 12 on one page.
- Black CI build time and cost
- GitHub CLI CI build time and cost
- Codex CLI CI build time and cost
- Flask CI build time and cost
- Guava CI build time and cost
- AI SDK CI build time and cost
- Pydantic CI build time and cost
- TypeScript CI build time and cost
- Vite CI build time and cost
- Vue CI build time and cost
- fd CI build time and cost
Where is the data?
/data/github-actions-benchmarks.json: runners, projects and commits, the summary rows, exclusions and every run with its log URL./data/github-actions-benchmarks.csv: one line per project and runner, with the project commit, the cost per build and the median run’s log URL.
Prices per minute for every runner are on Sengi pricing and in the runner comparison.
Frequently asked questions
How long does Mastodon CI take on GitHub Actions and on Sengi?
Measured November 17, 2026, at commit 3987b9f of mastodon/mastodon: GitHub-hosted 4 vCPU took 153 s median over 4 runs, $0.036 a build; Sengi Basic 4 vCPU took 168 s median over 3 runs, $0.006 a build, 10% more time and 83% less cost against GitHub-hosted 4 vCPU; Sengi Premium 4 vCPU had not enough runs (2 measured, 1 failed), so no median is printed. Times are median job seconds at 4 vCPU, printed only with at least 3 runs.
What does one Mastodon build cost?
Cost is billed minutes, each job rounded up to a whole minute, at the list price: GitHub-hosted 4 vCPU $0.012 a minute, Sengi Basic 4 vCPU $0.002 a minute and Sengi Premium 4 vCPU $0.006 a minute. Per build: GitHub-hosted 4 vCPU $0.036, Sengi Basic 4 vCPU $0.006.
What does the Mastodon job run?
Docker image build (linux/amd64) after a one-file change, layer cache on. Language: Docker. Repository: mastodon/mastodon, pinned to commit 3987b9fd624010eeeaeb7cad96606b05aa813f6a.
Did Sengi take more time than GitHub’s runner on Mastodon?
At 4 vCPU, Sengi Basic 4 vCPU took more time than GitHub-hosted 4 vCPU: 168 s against 153 s. Not like-for-like with GitHub’s 4 vCPU runner: Sengi Basic 2 vCPU took more time than GitHub-hosted 4 vCPU. Every result is in the tables on this page.
Why does the comparison use 4 vCPU?
The benchmark runs in a public repository so that every run log is public, and GitHub’s ubuntu-24.04 runner measured 4 vCPU there (nproc inside each job). Sengi runners with the same vCPU count are compared with it directly; Sengi Basic 2 vCPU has half the cores of GitHub’s 4 vCPU runner, and Sengi Premium 2 vCPU has half the cores of GitHub’s 4 vCPU runner, so they are shown separately and not as a like-for-like comparison.
Why is GitHub’s runner priced if public repositories are not billed for it?
GitHub does not bill public repositories for its standard runner, which is 4 vCPU there. The GitHub column is priced at GitHub’s listed rate for its 4 vCPU Linux larger runner (sold to Team and Enterprise Cloud organizations), $0.012 a minute: what a private repository pays for these minutes beyond its plan’s included usage.
Can I check the Mastodon numbers?
Yes. Every printed median links to the log of the run nearest that median in the public repository sengirunners/benchmarks, at commit e73c896. Every run, failed ones included, is in the JSON file on this page, and the CSV file has one line per project and runner.
Keep your workflow. Cut your runner rate.
Sengi Basic starts at $0.001 a minute for 2 vCPU. Choose 4 or 8 vCPU for $0.002 or $0.004 a minute. Premium stays optional at $0.003, $0.006 and $0.012.
Start without a card ↗︎