Is there any alternative way to constrain max physical RAM that Ignite uses?
My use case is to constrain physical RAM usage in a shared environment, while allowing a relatively generous allocation of swap storage. I'm aware of Ignite persistence, but believe that swap storage might meet our needs better in this case. So ideally, I'd configure the memory region max memory to determine the size of the swap file - and use some other parameter to configure the maximum amount of off-heap RAM that the process can consume. What is the best way to achieve this? Thanks, Colin. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
