Skip to content

Commit efd63cb

Browse files
Update note on container limits and JVM heap usage
Clarify note about deploying without container limits and its impact on JVM heap allocation.
1 parent a47d0a7 commit efd63cb

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

‎modules/container-resource-detection/pages/determining-cpu-availability-within-containers-openshift.adoc‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ oc new-project hotrod-s2i-project
1616
oc new-app registry.access.redhat.com/ubi9/openjdk-17~https://github.com/alexbarbosa1989/hotrodspringboot.git --name=hotrod-app
1717
----
1818

19-
NOTE: Deploying as above will be without container limits, therefore it will use the host limits. This has implications for heap usage. For example, `Compressed Oops` mode will come disabled if the heap size is more than 32Gb+ and the VM.info will not show the line `Heap Address`.
19+
NOTe: The deployment above (oc new-app`) does not set container limits, it will default to the host's limits. This directly impacts JVM heap allocation; for example, if the heap size exceeds 32 GB, Compressed Oops will automatically be disabled, and the Heap Address line will be omitted from the VM.info output.
2020

2121
. Use the following command to check the status of the deployment:
2222
+

0 commit comments

Comments
 (0)