chore: increase minCapacity for gecko-1/decision #750
+2
−1
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
At the moment, p50 pending for decision tasks on Try sits at 0s, while p95 ranges from 90s to 200s. The data shows that this is inversely correlated with the number of action tasks running (ie: p95 goes up when there are fewer action tasks). This makes sense, because they share this pool, and the action tasks are lower priority than decision tasks. This suggests to me that we may be able to reduce p95 for the decision tasks by having more workers always available. Additionally: * Most hours of most days see more than 5 tasks per hour (with double and even triple digits being common at certain days/times) * The cost of this pool now is next to nothing (~$15 in the past week) With all of this in mind, I'd like to try raising minCapacity to see if it will improve p95 pending.
Contributor
This doesn't match https://searchfox.org/firefox-main/rev/93aad2a6615f670b1279c229dd37f7397236131a/.taskcluster.yml#179-194? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
At the moment, p50 pending for decision tasks on Try sits at 0s, while p95 ranges from 90s to 200s. The data shows that this is inversely correlated with the number of action tasks running (ie: p95 goes up when there are fewer action tasks). This makes sense, because they share this pool, and the action tasks are lower priority than decision tasks. This suggests to me that we may be able to reduce p95 for the decision tasks by having more workers always available.
Additionally:
With all of this in mind, I'd like to try raising minCapacity to see if it will improve p95 pending.