feat(runtime): automatically optimize Go runtime based on cgroup limits #1839
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
weisdd
requested review from
NissesSenap,
ishanjainn,
theSuess,
hubeadmin and
pb82
as code owners
theSuess
approved these changes
Jan 28, 2025
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.
To make Go runtime aware of CGroup limits, added two calls that set appropriate values for
GOMEMLIMIT(affects GC schedule) andGOMAXPROCS(affects number of OS threads that can execute user-level Go code simultaneously).If the operator is deployed without resource limits, then
GOMEMLIMITandGOMAXPROCSwill not be set.If the respective environment variables are already present, then no changes are made.