analysis: usage analysis and new queue analysis for 2025-12-02 #84
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
69f3c86 to
7f5fd65
Compare
jschwe
reviewed
Dec 2, 2025
Comment on lines
+29
to
+30
| those workflow runs include 655 job runs that were allowed to reserve self-hosted runners, of which 611 actually used self-hosted runners, which is a 93.2% success rate. | ||
|
|
Member
There was a problem hiding this comment.
Sounds like we should work on allowing more jobs to run self-hosted runners then.
jschwe
approved these changes
Dec 2, 2025
sagudev
reviewed
Dec 2, 2025
Member
sagudev
left a comment
There was a problem hiding this comment.
LGTM
and it looks like this got merged while I was reading it
Member
There was a problem hiding this comment.
Well we do profit from having self-hosted runners so that is something.
Maybe we can reduce IDLE time by having running some expensive scheduled jobs (webgpu CTS, wpt runs, coverage). How much idle time is actually "in one slice"?
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
unfortunately neither the new global queueing feature (servo/servo#40852), nor dropping the runner-timeout jobs (servo/servo#40876), have improved self-hosted runner utilisation (a metric of server workload).
that said, the self-hosted runner hit rate is 93%, so not too many jobs are missing out on self-hosted runners.