Starting from Java 10, this parameter (which is enabled by default) is used to make the JVM take the container memory limits into account when allocating the heap size, not the host machine configuration.
This option was backported to Java 8:
https://www.oracle.com/technetwork/java/javase/8u191-relnotes-5032181.html
Examples:
If you run:
docker run **-m 1gb** openjdk:8u131 java -XshowSettings:vm -version
The result is going to be (on my machine Ubuntu with 8gb)
Max. Heap Size (Estimated): 1.68G
I set a memory limit for the container but it ignored and used the host config (it uses by default total memory/4)
Now if I run the version that has the new feature (link above) you can see that the container memory limite was taken into account:
docker run **-m 1g** openjdk:8u191-jre-alpine java -XshowSettings:vm -version
Result (total memory / 4):
VM settings:
Max. Heap Size (Estimated): 247.50M
Ergonomics Machine Class: server
Using VM: OpenJDK 64-Bit Server VM
openjdk version "1.8.0_191"
At the time I'm writing this the LATEST version of the openjdk:8 image is 222 so you can use this version. That has the feature included.
For more information:
Explains this flag use in Java 10: https://medium.com/adorsys/jvm-memory-settings-in-a-container-environment-64b0840e1d9e
Using this flag with Java 8: https://blog.softwaremill.com/docker-support-in-new-java-8-finally-fd595df0ca54
与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…