Open
Conversation
odra
force-pushed
the
meminfo
branch
3 times, most recently
from
02950e1 to
b48c44c
Compare
Contributor
Author
|
retest this please |
|
@odra - One question ? - have you tracked the values you get against the actual heap in the VM. I'm not sure that this will do it - its is still just monitoring the container rather than the vm |
Contributor
Author
|
@luigizuccarelli I was able to get the max jvm heap size by running |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Gets used memory from
/proc/meminfofile.ping @luigizuccarelli @maleck13