Hi, There is a capacity planning guide [1] that lists how the memory is consumed by Ignite and how you can control it.
The first thing is that if you have a single backup then the amount of is doubled. Next, remove this setting giving a chance to Ignite pre-allocating the size it will need in practice This property doesn't have any effect at all for off heap caches <bean class="org.apache.ignite.cache.eviction.lru.LruEvictionPolicy"> <property name="maxSize" value="100000"/> </bean> Finally, how many indexes do you have per object? Indexes are not free as [1] states. Also make sure that there are no "unable to marshall with BinaryMarshaller" like messages in the logs, otherwise it would mean that values won't be serialized and stored in size optimal way. -- Denis [1] https://apacheignite.readme.io/docs/capacity-planning -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Ignite-used-memory-7-times-greater-than-imported-data-tp6225p6293.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
