chore: perform rss/wss-aware cgroups memory usage calculation #3052
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.
Description
Previous calculation of memory usage under cgroups was not taking into consideration RSS & WSS memory, it was relying only to
memory.usage_in_bytes
which can be imprecise under circumstances. This article explains how k8s actually calculates RSS & WSS memory respectively.With this change, we are now calculating both RSS & WSS values and consider the greatest one to be equal to the actual memory usage.
Note: verified in
prousmt
environment where this inconsistency was initially observed.Notion Ticket
Link
Security