Skip to content
RunsOn
Blog

GitHub Actions Runners Benchmark

This page offers a detailed comparison of CPU speeds and queuing times for various providers of GitHub Actions runners. The aim is to assist in identifying the best GitHub Actions runner provider for your projects, based on your specific needs.

Providers included in the benchmark:

Key metrics such as the processor model, single-thread CPU speed, queue time, pricing, and the underlying infrastructure provider are compared. The CPU single-threaded rating is a crucial metric as it is the most significant factor (unless your job is massively parallel) in accelerating any of your workflows.

Note that x64 and arm64 CPU speed numbers are not directly comparable.

An analysis is provided below the benchmark results. Note that this benchmark is published by RunsOn, but I try my best to provide a fair comparison with the details available.

Results

x64 runners

Provider Processor CPU speed
(p50 | p95) 		Queue time (s)
(p50 | p95) 		Infra Samples
Namespace (2x cheaper)
  • nscloud-ubuntu-22.04-amd64-2x8
 AMD EPYC (x86_64) 3890 | 3989 20 | 24 Hetzner Online 30
Buildjet (2x cheaper)
  • buildjet-2vcpu-ubuntu-2204
 AMD Ryzen 9 7950X3D 16-Core Processor (x86_64) 3886 | 4005 22 | 24 Hetzner Online 9
Buildjet (2x cheaper)
  • buildjet-2vcpu-ubuntu-2204
 AMD Ryzen 9 5950X 16-Core Processor (x86_64) 3230 | 3456 24 | 26 Hetzner Online 21
Blacksmith (2x cheaper)
  • blacksmith-2vcpu-ubuntu-2204
 AMD EPYC (x86_64) 3320 | 3563 24 | 39 Hetzner Online 30
Cirrus (fixed price per runner)
  • ghcr.io/cirruslabs/ubuntu-runner-amd64:22.04-md
 Intel Xeon Gold 5412U (x86_64) 3238 | 3246 21 | 27 Hetzner Online 30
RunsOn (10x cheaper)
  • runs-on,family=r7iz
 Intel Xeon Gold 6455B (x86_64) 3155 | 3160 31 | 34 Amazon.com 30
RunsOn (10x cheaper)
  • runs-on,family=c7a
 AMD EPYC 9R14 (x86_64) 2902 | 2904 31 | 34 Amazon.com 30
RunsOn (10x cheaper)
  • runs-on,family=m7i-flex
 Intel Xeon Platinum 8488C (x86_64) 2734 | 3019 33 | 37 Amazon.com 30
Warpbuild (2x cheaper)
  • warp-ubuntu-2204-x64-2x
 AMD EPYC 9R14 (x86_64) 2901 | 2904 17 | 57 Amazon.com 30
Ubicloud (10x cheaper)
  • ubicloud-standard-2
 AMD EPYC 9454P 48-Core Processor (x86_64) 2575 | 2595 17 | 38 Hetzner Online 30
GitHub
  • github-16cpu-x64
  • ubuntu-latest
 AMD EPYC 7763 64-Core Processor (x86_64) 2295 | 2401 11 | 16 Microsoft Azure 54

arm64 runners

Provider Processor CPU speed
(p50 | p95) 		Queue time (s)
(p50 | p95) 		Infra Samples
Warpbuild (2x cheaper)
  • warp-ubuntu-latest-arm64-2x
 (aarch64) 1546 | 1551 13 | 21 Amazon.com 30
RunsOn (10x cheaper)
  • runs-on,family=m7g
 (aarch64) 1546 | 1550 32 | 36 Amazon.com 30
Cirrus (fixed price per runner)
  • ghcr.io/cirruslabs/ubuntu-runner-arm64:22.04-md
 Neoverse-N1 (aarch64) 1325 | 1327 23 | 24 Hetzner Online GmbH 30
Buildjet (2x cheaper)
  • buildjet-2vcpu-ubuntu-2204-arm
 Neoverse-N1 (aarch64) 1322 | 1325 38 | 39 Hetzner Online 30
GitHub
  • github-2cpu-arm64
 Neoverse-N1 (aarch64) 1320 | 1324 13 | 15 Microsoft Azure 24
Ubicloud (10x cheaper)
  • ubicloud-standard-2-arm
 Neoverse-N1 (aarch64) 1318 | 1322 16 | 18 Hetzner Online 30
Namespace (2x cheaper)
  • nscloud-ubuntu-22.04-arm64-2x8
 Neoverse-N1 (aarch64) 1313 | 1318 23 | 24 Hetzner Online 30

Analysis

What are the best providers for GitHub Actions runners?

The best provider for GitHub Actions runners will heavily depend on your primary requirement:

  • Fastest machines: Buildjet, Namespace, Cirrus (x64, arm64, macOS), and Blacksmith (x64 only) are good choices. Be aware that they are hosted at Hetzner, with variable performance for the network speeds. Buildjet also doesn’t guarantee you to end up on one of their fastest runners.

  • Cheapest pricing: RunsOn, Ubicloud, or Cirrus (if ok with limited concurrency) are the best options. Be aware that Ubicloud has a slightly lower CPU speed and somewhat variable queue times for x64 (but improving).

  • Low queue times: GitHub has the best queue time, and all third-parties are good on that front.

  • On-premise deployment: RunsOn is the only solution that is entirely hosted in your AWS infrastructure, with no third-party centralized service.

  • All rounder: RunsOn is a good option, due to top-of-the-line CPU speeds (especially ARM64), cheapest pricing, stable queue times across x64 and arm64, and the ability to deploy on-premise. If you need MacOS machines, Cirrus or Warpbuild are good choices. If you cannot use AWS and want the cheapest prices, try Ubicloud.

When should I use GitHub’s official Action runners?

GitHub’s official Action runners are best used for short-lived jobs or those that do not require fast CPUs. They boot quickly, making them ideal for smaller, less intensive tasks. However, for larger or more CPU-intensive jobs, consider alternative runners due to the slower performance and higher costs of GitHub’s larger runners.

About those benchmarks

Benchmarks are performed using the Passmark benchmarking tool ↗, using the CPU Single Threaded metric.

The table displays the last 30 days of data, before the last updated date.

Last updated: