Hi, what exactly is not clear? When you create objects in Java, they end up on JVM heap, in managed memory. These objects are subject to automatic garbage collection. Ignite Off-Heap Memory feature stores cache data in unmanaged memory (manual allocation/deallocation, like you do in C and other unmanaged languages). This reduces GC load (better performance, less GC pauses).
Let me know if this helps. Pavel. On Thu, May 5, 2016 at 5:08 PM, tomk <rrrtomtom...@gmail.com> wrote: > Hello, > Could someone explain this in simpler way ? Maybe some intuition ? > > > > -- > View this message in context: > http://apache-ignite-users.70518.x6.nabble.com/Off-Heap-Memory-simpler-explanation-than-in-docs-tp4790.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com. >
