Hi, I am trying to understand the support in Ignite for spilling over to disk when memory limits are reached.
I see there is a feature of swap space as in the link below, https://apacheignite.readme.io/docs/off-heap-memory#swap-space But, I am not clear on how it works. When we configure swap-space it appears the cached data would be stored in swap space. But, what would the change be from the perspective of client. Is it completely transparent to the client. I do understand that there would be a performance impact if it is enabled, as it would slow the cache operations as some data would be in memory and some in disk. Does this feature work and can we rely on it for critical scenarios where we expect data size to be more which cannot be accommodated within the configured memory limits. Also, is there a way we can configure it per cache and not globally so that for some items alone it can spill over to disk -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Understanding-Swap-Space-feature-how-it-works-tp10859.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
