Rightsize resource requests for Release app. #1121
Merged
Conversation
This file contains 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
WSS has never gone above 200 MiB and CPU usage is tiny. Also reduce server replica count to 2 (since this is an internal dashboard with a very low request rate) and worker count to 1 (since all the worker does is forward messages to Slack, so if it gets reschedule then it'll just add a few seconds of delay to an already not-guaranteed message). This offsets the extra cost of the recently-added worker deployment.
theseanything
approved these changes
May 23, 2023
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.
WSS has never gone above 200 MiB and CPU usage is tiny.
Also reduce server replica count to 2 (since this is an internal dashboard with a very low request rate) and worker count to 1 (since all the worker does is forward messages to Slack, so if it gets rescheduled then it'll just add a few seconds of delay to an already not-guaranteed message).
This offsets the extra cost of the recently-added worker deployment.