I would not recommend doing so, because it may affect Ignite performance,
but you can tweak JVM to use less memory and return it to OS more
frequently like this:
var cfg = new IgniteConfiguration
{
ClientMode = true,
JvmOptions = new[]{"-XX:MaxHeapFreeRatio=30", "-XX:MinHeapFreeRatio=10"},
JvmInitialMemoryMb = 100,
JvmMaxMemoryMb = 900
};
On Mon, Nov 18, 2019 at 3:42 AM camer314 <[email protected]>
wrote:
> Ok yes i see. Seems like with my code changes I made to provide the example
> that the memory consumption is way more inline with expectations, so I
> guess
> it was a code error on my part.
>
> However, it seems strange that my client node, which has no cache, still
> wants to hang onto over 1Gb of heap space even though its using less than
> 100Mb. Is there no way to release that back?
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>
