-
Notifications
You must be signed in to change notification settings - Fork 100
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
looker: Update heap size calculation for cgroups #23
Open
mattrobenolt
wants to merge
1
commit into
looker-open-source:main
Choose a base branch
from
mattrobenolt:patch-1
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I kept this math the same, but using 60% feels a bit wrong to me, if your goal is to basically be
limKb = limKb - (1024 * 1024 * 1.5);
So let me know if you want me to accommodate for that instead, I just didn't wanna change behavior.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It seems imo, if we have a cgroup, we can set the limit to exactly the cgroup (maybe subtract a few MB to keep some breathing room), and apply the 60% or some -1.5GB of the value comes from the whole system's memory. If we're running within a container, I'm not sure why we'd need to have that much breathing room.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The JVM has support for containers now, so you can just use something like:
-XX:MaxRAMPercentagerather=90.0
.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is probably irrelevant now since as you mentioned the JVM now supports automatically setting the heap size when it detects it is running in a container.
However, when running on Ubuntu 20.04.5 LTS the
/sys/fs/cgroup/memory/memory.limit_in_bytes
file seems to have been replaced by/sys/fs/cgroup/memory.max
.For me, running this in docker, the memory.max file stores the max memory limit in bytes.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Excuse my ignorance of cgroups, this seems to be a platform issue, when running Docker Desktop on MacOS
/sys/fs/cgroup/memory.max
is the file but when running on a Linux node the file was/sys/fs/cgroup/memory/memory.limit_in_bytes