Skip to content
This repository was archived by the owner on Jul 19, 2025. It is now read-only.

Set JVM heap size options #42

Merged
merged 1 commit into from
Nov 13, 2015
Merged

Set JVM heap size options #42

merged 1 commit into from
Nov 13, 2015

Conversation

jpignata
Copy link
Contributor

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?

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.
@gdiggs
Copy link
Contributor

gdiggs commented Nov 13, 2015

Worth a shot!

jpignata added a commit that referenced this pull request Nov 13, 2015
@jpignata jpignata merged commit 8a57a41 into master Nov 13, 2015
@jpignata jpignata deleted the jp/cap-java-memory-usage branch November 13, 2015 22:26
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants