Observability
How do I detect an undersized runner?
Quick answer
Sustained CPU near 100%, memory pressure, or swap activity through the job.
The detail that matters
High I/O wait with low CPU means the opposite problem — you need faster disk, not more cores.
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
How do I see cost per workflow?The runnerhut dashboard breaks spend down by workflow, job, label and repository.How do I see cost per runner label?Filter the usage dashboard by label to see minutes and spend per runner type.How do I find the slowest step in a workflow?Sort steps by duration in the run view, or use the runnerhut timeline which shows queue, setup and step time separately.How do I find which workflow got slower?Compare p95 duration per workflow month over month in the analytics dashboard.