Increase CPU allocation for triagebot to one full CPU - #1222
Merged
Conversation
marcoieni
approved these changes
Sep 2, 2026
|
Are the additional resources needed? |
Member
|
I'll apply once you have an agreement in the team |
Member
Author
Having more RAM is useful to cache more entries in our GitHub viewers. And generally increasing resources should lessen latencies a bit. |
marcoieni
force-pushed
the
triagebot-hw
branch
from
September 4, 2026 15:14
2fd14c0 to
c1b7b78
Compare
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
3 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.
Apparently, we should be spending more credits 😆 So why not give a whopping full CPU to triagebot, instead of a quarter (!) of a CPU that it had previously.
CC @rust-lang/triagebot