Customize GC behavior differently #96
Merged
Conversation
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
By default, the JVM does not free allocated heap back to the OS. This configures away from that behavior, hopefully to prevent OOM engine errors. It replaces the existing configuration which put absolute size limits on the heap. See http://www.stefankrause.net/wp/?p=14 for details on the specific options chosen. This configuration brought my test repository's memory usage down from ~700MB to ~250MB. Its graph also shows most closely the pattern we'd prefer: the slope of allocated heap closely matching used.
|
👍 Nice find. |
pbrisbin
added a commit
that referenced
this pull request
Feb 3, 2016
Customize GC behavior differently
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.
By default, the JVM does not free allocated heap back to the OS. This
configures away from that behavior, hopefully to prevent OOM engine errors. It
replaces the existing configuration which put absolute size limits on the heap.
See http://www.stefankrause.net/wp/?p=14 for details on the specific options
chosen. This configuration brought my test repository's memory usage down from
~700MB to ~250MB. Its graph also shows most closely the pattern we'd prefer:
the slope of allocated heap closely matching used.
/cc @codeclimate/review
This fix was first discovered while working on
kibit. I realized this
tuning is probably good for any JVM-based engine.