Perhaps you can try some experiments like this:
› docker run -m 500MB openjdk:8 java -XX:MaxRAMPercentage=60.0
-XshowSettings:vm -version
VM settings:
Max. Heap Size (Estimated): 290.00M
Ergonomics Machine Class: server
Using VM: OpenJDK 64-Bit Server VM
openjdk version "1.8.0_242"
OpenJDK Runtime Environment (build 1.8.0_242-b08)
OpenJDK 64-Bit Server VM (build 25.242-b08, mixed mode)
My thought is that you will likely have better results if you can rely on known
heap sizes that perform well for the given workload. If there is insufficient
memory available for the data you want to store in geode, you are likely to see
poor performance due to excess GC overhead and potentially cluster instability
if the overloaded container is unresponsive.
YMMV,
Anthony
> On Oct 19, 2021, at 2:06 PM, Thomas Enblom <thomas.enblo...@gmail.com> wrote:
>
> Hi
>
> I have two questions on how large the heap size in a Geode will be using the
> new parameter XX:maxRAMPercentage in a kubernetes cluster under the following
> conditions:
>
> 1) My JVM container has only (in the helm chart) Memory Request set but
> Memory Limit NOT set in order to obtain Best Effort memory use. Since
> XX:maxRAMPercentage is in relation to the Limit, and there is no limit set,
> then what heap size will be obtained?
>
> 2) My JVM container has NOT defined (in the helm chart) Memory Request and
> Memory Limit in order to obtain Best Effort memory use. Since
> XX:maxRAMPercentage is in relation to the Limit, and there is no limit set,
> then what heap size will be obtained?
>
> BR, Thomas
