Performance
How fast do runners start after a job is queued?
Quick answer
runnerhut runners start in about three seconds from a warm pool.
The detail that matters
Cold-booting a VM per job takes 30–90 seconds. On short jobs that overhead is larger than the work itself.
Your next build could be twice as fast, at half the price
Start free. Migrating away is the same one line, and we publish that diff too.
Related
Why are GitHub Actions slow?Most commonly: shared vCPU, cold caches, network-attached disk, and queue time before the job even starts.Do I need to change my workflow?No. Change the runs-on label and leave everything else as it is.How do I choose a runner size?Start one size above your current runner, then check CPU utilization and stop when the curve flattens.Why do my jobs queue behind each other?You have hit a concurrency limit — either your plan's, your runner group's, or a concurrency group in the workflow.