Ok, I have done more research and I think I understand the effect of these
two parameters. I think my original question is resolved.
Also, I have found that this parameter has a huge performance impact as
well:
<bean class="org.apache.ignite.configuration.CacheConfiguration">
...
<property name="eagerTtl" value="false"/>
...
</bean>
When eagerTtl is true (default), Ignite will start a thread per cache to try
to delete entries as quick as possible. I was running tests with 1,000
caches and the number of threads was overwhelming the nodes.
Thanks for all your help!
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Ignite-Cache-High-Memory-Overhead-caused-by-GridCircularBuffer-Item-instances-tp3682p3719.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
