GitHub Community
[Question]: How is the "Avg queue time" in GitHub Actions Insights calculated? #191940
-
Discussion TypeQuestion Discussion ContentWhy are you starting this discussion? What GitHub Actions topic or product is this about? Discussion Details |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
|
The “Avg queue time” shown in GitHub Actions Insights reflects the time a job spends in the GitHub queue before the runner starts executing. It doesn’t include every delay outside of job setup — once the runner begins the Set up job phase, that part is no longer considered queue time in the Insight metric. |
Beta Was this translation helpful? Give feedback.
-
|
thankyou |
Beta Was this translation helpful? Give feedback.
-
|
Yes, because in GitHub Actions, “Avg queue time” only measures the duration from when a job is triggered until a runner starts picking it up; once the job enters the “Set up job” phase, it is no longer considered queued. With self-hosted runners using Azure Arc, delays such as pod scheduling, image pulling, or init container execution happen after this point, so they are counted as part of the job’s execution time rather than the queue time. |
Beta Was this translation helpful? Give feedback.
The “Avg queue time” shown in GitHub Actions Insights reflects the time a job spends in the GitHub queue before the runner starts executing. It doesn’t include every delay outside of job setup — once the runner begins the Set up job phase, that part is no longer considered queue time in the Insight metric.
So if your self-hosted runner’s init container is waiting on resources before the Actions runner actually starts, that wait isn’t counted in the average queue time shown in Insights. The metric focuses on the time between when GitHub schedules the job and when it actually starts running on a runner.