Set system property for experimental memory-limit based heap settings #324
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
Generate changelog in
|
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.
Before this PR
Currently, we set a blanket RAM percentage of 75% irrespective of the actual memory limits of the execution environment or the non-heap demands we might have. We'd like to adjust this moving forward, but need to do so in a conservative fashion to limit any production impact. This PR adds a system property which we can use to emit metrics and gather data on what a reasonable "heap scaling" function should look like.
After this PR
==COMMIT_MSG==
Set system property for experimental memory-limit based heap settings. Enabling this will allow gathering data on real workloads without any behavioral changes.
==COMMIT_MSG==
Possible downsides?