Allowed MEMORY to be unset and let JVM calculate from container

#742
This commit is contained in:
Geoff Bourne
2021-10-31 09:42:27 -05:00
parent c7f1d13f9b
commit 3713d9c4e8
2 changed files with 19 additions and 9 deletions
+3 -1
View File
@@ -1288,7 +1288,9 @@ The values of all three are passed directly to the JVM and support format/units
-e MEMORY=2G
> NOTE: the settings above only set the Java **heap** limits. Memory resource requests and limits on the overall container should also account for non-heap memory usage. An extra 25% is [a general best practice](https://dzone.com/articles/best-practices-java-memory-arguments-for-container).
> To let the JVM calculate the heap size from the container declared memory limit, unset `MEMORY` with an empty value, such as `-e MEMORY=""`.
> The settings above only set the Java **heap** limits. Memory resource requests and limits on the overall container should also account for non-heap memory usage. An extra 25% is [a general best practice](https://dzone.com/articles/best-practices-java-memory-arguments-for-container).
### JVM Options