chore(elasticsearch): reduce CPU requests and limits on production #1261
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
m90
reviewed
Nov 14, 2023
| memory: "64Gi" | ||
| limits: | ||
| cpu: "10" | ||
| cpu: "4" |
There was a problem hiding this comment.
This seems pretty drastic to me right now (even if it does not seem to use more). I wouldn't mind if we maybe start a little more conservative and see if it behaves well still? In the end, we probably also should consider the size of instances we can get as we need to provision a lot of memory. If this means we have spare CPUs doing nothing at all all the time, we might wanna allocate them here.
m90
approved these changes
Nov 14, 2023
tarrow
approved these changes
Nov 15, 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.
No description provided.