kubernetes: gtfs-rt-archive: lower memory limit and add cpu request #1540
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
The memory limit of 2 GB is well above normal operating range, and in fact tends to indicate that there is already a problem well underway. A review of grafana data suggests that normal operation should remain under the 512 MB mark. The lack of CPU requests also means that both the preprod and the prod archiver instances may end up scheduled on the same node, which in the event of a utilization spike over 4 cores, could cause transaction failures. This CPU request reflects more than half of the capacity of any given node in the gtfsrt-v1 pool, reasonably ensuring that preprod and prod instances will not be co-scheduled on a node.
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.
The memory limit of 2 GB is well above normal operating range, and in
fact tends to indicate that there is already a problem well underway. A
review of grafana data suggests that normal operation should remain
under the 512 MB mark.
The lack of CPU requests also means that both the preprod and the prod
archiver instances may end up scheduled on the same node, which in the
event of a utilization spike over 4 cores, could cause transaction
failures. This CPU request reflects more than half of the capacity of
any given node in the gtfsrt-v1 pool, reasonably ensuring that preprod
and prod instances will not be co-scheduled on a node.