ignite-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Artem Shutak <ashu...@gridgain.com>
Subject Re: Reducing On-Heap Cache Memory Footprint
Date Mon, 04 Apr 2016 15:30:09 GMT
Hello,

I would suggest you to follow the following algorithm when calculating
memory usage by Ignite.

CALCULATING THE MEMORY USAGE
1. Calculate primary data size: multiply the size of one entry in bytes by
the total number of entries. Note, that Ignite will typically add around 200
bytes overhead to each entry.
2. If you have backups, multiply by their number
3. Indexes also require memory. Basic use cases will add a 30% increase
4. Add around 20MB per cache. This value can be reduced if to decrease
partitions count and/or
IgniteSystemProperties.IGNITE_ATOMIC_CACHE_DELETE_HISTORY_SIZE
5. Add around 200-300MB per node for internal memory and reasonable amount
of memory for JVM and GC to operate efficiently

So, in your case with 1 node and 0 backups it is:

(24+32+200)*2_000_000 bytes + 20 mb + 200 mb > 700 mb.

Thanks,
- Artem -



--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Reducing-On-Heap-Cache-Memory-Footprint-tp3836p3909.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Mime
View raw message