Hello, You need take care, when dedicate minimum heap size, because JVM does not work with unsave memory directly. Copy data from off-heap to heap and deserialize occur over each cache operation (like get, getAll, execute query). Exception (Out of memory) will be thrown if heap was overflowed.
You can follow off-heap usage using cache metrics: cache.metrics().getOffHeapAllocatedSize() Not need to install heap size is too small, It should be sufficient for the storage of samples. On Wed, Aug 17, 2016 at 7:06 PM, yucigou <[email protected]> wrote: > If I understand correctly, JVM GC takes care of the on-heap memory. My > question is, who is going to take care of the off-heap memory? > > I guess the answer is Ignite :-) > > But something I'm not so sure is, can I just make all caches off-heap, and > my JVM GC will work with minimal memory, so that my application latency and > throughput would be maximised. Is this true? Will the reclamation of > off-heap memory cause any latency to the application, or lower the > application throughput as Ignite threads run concurrently. > > Is there a way to monitor the off-heap activities, which is similar to > Visual GC in JVisualVM? > > Could you help give some insight please? Also any best practice here? Thank > you. > > > > -- > View this message in context: http://apache-ignite-users. > 70518.x6.nabble.com/Who-is-going-to-take-care-of-the-off- > heap-memory-tp7138.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com. > -- Vladislav Pyatkov
