Repository navigation
builder: optionally check queue length before builds & limit max prio - #3676
Merged
Merged
Conversation
github-actions
Bot
added
S-waiting-on-review
Member
Author
GuillaumeGomez
approved these changes
Nov 5, 2026
Member
|
Thanks! |
GuillaumeGomez
enabled auto-merge (rebase)
November 5, 2026 13:51
github-actions
Bot
added
S-waiting-on-deploy
GuillaumeGomez
temporarily deployed
to
github-pages
November 5, 2026 13:56 — with 
GitHub Actions
Inactive
GitHub Actions
Inactive
This branch was previously deployed
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
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.
When digging into webserver performance issues on our legacy instance I saw one thing: running builds might make the webserver slower.
Since:
I thought about this feature, where we would deactivate initially 2 of the 6 builders if the queue is short enough. Also, these would only be used for release builds, not automated rebuilds.
Both the min-queue-length and the max-priority for these additional builders can be configured.
With the new infra we might not need this any more, since we have separate EC2 instances for each builder, and we can autoscale them.
But as long as that migration is not finished, I would like the option to reduce build speed, when it impacts the webserver too much, and while keeping the additional builders configured for "queue is full" situations.