Thanks for the responses. To summarise: * JVM Heap (Xmx) - Not normally used by Ignite for caching data. * MaxDirectMemorySize - Used by Ignite for some file operations but not for caching data. As per above, 256m is usually sufficient. * DataRegion maxSize - Used by Ignite to determine how much memory to allocate using some combination of durable, swap and off-heap (Java unsafe) RAM.
In my case, I have configured swap storage (https://apacheignite.readme.io/docs/swap-space) but *not* Ignite durable memory. If DataRegion maxSize is say 100GB and my physical RAM is 50GB then the swap file will be 100GB but Ignite will also use some portion (<50GB) of the available physical RAM for off-heap cache data storage. My question is about how to limit the size of this portion while still allowing the DataRegion to specify a large swap file for use as overflow of less regularly accessed data. For example, say I wanted my node to use 8GB off-heap physical RAM and 100GB swap file on a machine that has a total of 50GB of physical RAM (shared with other processes). What parameter would I need to configure 8GB? Is it possible to control this? Thanks, Colin. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
