Skip to content

Set Java Heap settings #57

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Dec 18, 2015
Merged

Set Java Heap settings #57

merged 1 commit into from
Dec 18, 2015

Conversation

wfleming
Copy link
Contributor

Starting heap 512mb, max heap 1.25GB.

👀 @codeclimate/review

@wfleming
Copy link
Contributor Author

Sigh. JVM behavior can be strange & confusing.

Setting only the initial heap failed tests because it was larger than the default max heap. Which is strange because docs say it's either 64MB (really?) or 1GB, but you can also query for it at runtime, which I did in container and the value was, I think, Java's max int value. So I think we were really getting getting the 64mb max heap, which is too small.

@wfleming wfleming changed the title Set starting Java Heap to 512mb Set Java Heap settings Dec 18, 2015
@@ -25,4 +25,6 @@ RUN npm install

USER app

ENV JAVA_OPTS="-Xms512m -Xmx1536m"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe add a comment above this of what each of these do?

@gdiggs
Copy link
Contributor

gdiggs commented Dec 18, 2015

One comment but otherwise LGTM

Starting heap 512mb, max heap 1.25GB.
wfleming added a commit that referenced this pull request Dec 18, 2015
@wfleming wfleming merged commit 71a96db into master Dec 18, 2015
@wfleming wfleming deleted the will/starting-heap branch December 18, 2015 16:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants