> If you know cache size, good practice define it in cache configuration > <property name="memoryMode" value="OFFHEAP_TIERED" />
It makes sense to switch to OFFHEAP_TIRED mode only if you are sure that all the caches will occupy more ~ 10 GB of Java heap. If the total size of all the caches is relatively small on a single cluster node then it’s ok to keep using ONHEAP_TIRED. > <property name="startSize" value="6500000”/> Don’t think that it makes sense to do so since it will increase Java heap usage that you’re suggesting to reduce. So, I would check that there is no long GC pauses happening during preloading. Refer to this doc on how to enable GC logs [1]. Next use ‘dstat’, ‘top’ or other system level tool to check that there is no swapping, CPU stagnation or network overflow during the preloading. [1] https://apacheignite.readme.io/docs/jvm-and-system-tuning#section-detailed-garbage-collection-stats <https://apacheignite.readme.io/docs/jvm-and-system-tuning#section-detailed-garbage-collection-stats> — Denis > On Jul 10, 2016, at 1:23 AM, AndreyVel <[email protected]> wrote: > > Hello Level D, > > I suppose you have gc performance problems. > Read JVM and System Tuning [1], article which provides general > recommendations on how to tune the GC and JVM. > > If you know cache size, good practice define it in cache configuration > <property name="memoryMode" value="OFFHEAP_TIERED" /> > <property name="startSize" value="6500000"/> > > Also better preload cahes eqt + eqt_temp before use continuous query. > For controlling cache loading you can use CacheStoreAdapter [2] > > > [1] https://apacheignite.readme.io/docs/jvm-and-system-tuning > [2] http://apacheignite.gridgain.org/v1.2/docs/data-loading > > > > -- > View this message in context: > http://apache-ignite-users.70518.x6.nabble.com/LoadCache-tp6140p6196.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com.
