Use physical memory for stats of kubelet #1
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
|
Looks like a fix for kubernetes#112111 |
adam-jian-zhang
force-pushed
the
kubelet-mem
branch
from
7c4e8c0
to
43ec94a
Compare
This is a hack to make kubelet use physical memory for calculate memory usage of the node without changing the data structure which only accounts private working set and commited pages. We patch the second to include the difffrom phsical available memory to the sum of private working set and commited pages. After the change, memory usage = memoryPrivWorkingSetBytes + memoryCommittedBytes = totalPhys - AvailPhys
adam-jian-zhang
force-pushed
the
kubelet-mem
branch
from
43ec94a
to
b088b04
Compare
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.
This is a hack to make kubelet use physical memory for calculate
memory usage of the node without changing the data structure which
only accounts private working set and commited pages.
We patch the second to include the difffrom phsical available
memory to the sum of private working set and commited pages.
After the change,
memory usage = memoryPrivWorkingSetBytes + memoryCommittedBytes
= totalPhys - AvailPhys
What type of PR is this?
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: