GitHub Actions runner questions, answered
How do I make GitHub Actions faster and cheaper?
Most slow GitHub Actions jobs are held back by the machine and by missing caches, not by the workflow: on a private repository, ubuntu-latest is a 2 vCPU, 8 GB virtual machine that starts every job with a cold disk and no Docker layer cache. Cache dependencies and layers, run independent jobs in parallel, then move the jobs that are still slow to faster hardware by changing runs-on. Sengi runs them on AMD Ryzen 9 7950X3D bare metal boosting past 5 GHz with local NVMe, builds up to 1.9× faster than GitHub’s runner, from $0.003 a minute against GitHub’s $0.006.
Last checked October 23, 2026. Each answer below links to its own page, with the detail, a table where it helps, and its sources.
Every question, with its short answer
Questions teams ask about GitHub Actions runner speed, specs, price, security and switching, each answered in one line. For providers side by side, see the runner comparison.
Why is GitHub Actions so slow?
A 2 vCPU cloud VM, a cold disk and no layer cache on every job. Faster hardware and caching fix most of it.
How do I make GitHub Actions faster?
Cache dependencies and Docker layers, run jobs in parallel, then move the slow jobs to faster hardware.
What is the cheapest GitHub Actions runner?
Sengi: $0.003, $0.006 and $0.012 a minute at 2, 4 and 8 vCPU, half GitHub's price at 2 and 4 vCPU.
Are GitHub larger runners worth it?
More cores help parallel builds, but GitHub bills them from the first minute at $0.012 to $0.252 a minute.
How much do GitHub Actions minutes cost?
$0.006 a minute for standard Linux, $0.010 Windows, $0.062 macOS, after your plan's included minutes.
Can I use a faster CPU for GitHub Actions?
Yes: change runs-on to a runner on a faster CPU, such as a 5 GHz AMD Ryzen 9 7950X3D on Sengi.
How do I cache Docker layers in GitHub Actions?
Use docker/build-push-action with cache-from: type=gha and cache-to: type=gha,mode=max.
What is the best GitHub Actions runner alternative?
A managed runner you switch to with one runs-on line. Sengi pairs 5 GHz bare metal with the lowest per-minute rate of the major managed runners.
Do third-party GitHub Actions runners work with private repositories?
Yes. A GitHub App registers runners for the repositories you select; code, secrets and logs stay in GitHub.
How do I switch runs-on to another runner?
Replace the label in each job's runs-on line with the new runner's label, and merge.
How many CPU cores and how much RAM does a GitHub Actions runner have?
ubuntu-latest is 2 vCPU and 8 GB on private repositories, 4 vCPU and 16 GB on public ones, with a 14 GB SSD.
Are third-party GitHub Actions runners secure?
They can be: look for a fresh VM per job, repository-scoped access and secrets that stay in GitHub.
Why is my GitHub Actions job waiting for a runner?
No online runner matches its runs-on label, or a concurrency limit, group or approval is holding it.
Are self-hosted GitHub Actions runners cheaper?
Only at high volume: people time dominates, so a modelled fleet beats GitHub near 106,000 minutes a month.
Why is npm install slow in GitHub Actions?
No package cache, npm install instead of npm ci, and a disk-bound install on a slow disk.
How many GitHub Actions jobs can run at the same time?
20 on GitHub Free, 40 on Pro, 60 on Team and 500 on Enterprise Cloud, for standard hosted runners.
Why is my GitHub Actions bill so high?
Volume: matrix jobs, retries, superseded pushes and larger runners billed from the first minute.
Where are the longer guides?
- Faster GitHub Actions runners: what makes a runner fast, measured.
- GitHub Actions runner specs: CPU, memory and disk for every hosted runner.
- Slow Docker builds in GitHub Actions: causes, layer caching and fixes.
- Self-hosted runner alternative: managed runners against running your own.
- GitHub Actions pricing in 2026: every rate and plan allowance.
The fastest hardware for your GitHub Actions.
AMD Ryzen 9 7950X3D desktop CPUs boosting past 5 GHz, on bare metal with local NVMe, a fresh VM for every job, and 2 vCPU jobs ready in 2 seconds. Builds finish up to 1.9× faster than on GitHub’s runners, and at up to half GitHub’s price per minute they cost up to 74% less per build. Change one runs-on line, or give your coding agent one prompt and it opens the pull request for you.