Java in a Container: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
No edit summary
No edit summary
Line 2: Line 2:


* https://developers.redhat.com/blog/2017/03/14/java-inside-docker/
* https://developers.redhat.com/blog/2017/03/14/java-inside-docker/
* https://blog.softwaremill.com/docker-support-in-new-java-8-finally-fd595df0ca54
* https://stackoverflow.com/questions/54292282/clarification-of-meaning-new-jvm-memory-parameters-initialrampercentage-and-minr/54297753#54297753


=Internal=
=Internal=

Revision as of 22:56, 5 November 2019

External

Internal

Overview

When running java in a container, the max heap should always be set with -Xmx, based on the application needs and the container limits.

Java max heap limit can also be calculated based on the container limits.

Generic script that correlates JVM memory settings to the container limits: