Hi Arthi,
/I re-ran the tests with offheap tiered settings, and it looked very
neat. The heap usage was around 300MB./
//This is because all your cache data presently located out of Java heap
in the offheap space [1]
Offheap is very useful for cases when Java heap tends to grow to tens
and hundreds of gigabytes due to big amount of data stored in caches.
Big Java heaps are quite difficult and not always possible to tune which
leads to long GC pauses.
You can check the overall memory consumption using "top" or similar
command on Linux. Also you have IgniteCache.size(OFFHEAP!PRIMARY) at you
service.
Finally you can connect to the cluster with ignitevisorcmd.sh/bat and
look at the cache total size, offheap portion, etc.
[1] https://apacheignite.readme.io/docs/off-heap-memory
--
Denis
On 3/29/2016 9:13 PM, arthi wrote:
hi Denis,
I re-ran the tests with offheap tiered settings, and it looked very neat.
The heap usage was around 300MB. Please find the hist attached. I could not
take a profiler snapshot as it is a remote application and uses Java 7.
Thanks again,
Arthi
hist3328.1
<http://apache-ignite-users.70518.x6.nabble.com/file/n3745/hist3328.1>
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Cache-loading-errors-out-tp3636p3745.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
