This repository was archived by the owner on Jul 19, 2025. It is now read-only.
Set JVM heap size options #42
Merged
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.
We're seeing the duplication engine being killed for memory consumption
in production while analyzing medium-sized repositories. This change
sets an initial and maximum heap space of 384MB. This will keep us
under the memory limit while leaving additional working memory for
other processes.
This is kind of a shot in the dark. We're seeing this behavior only in production and not in the CLI. Thoughts, @codeclimate/review?