Re: Cache size in offheap mem in bytes

It's incorrect to use cache object to calculate cache data size. What you got now is a footprint of the Ignite infrastructure used to manage your data, but not a footprint of your data itself, since data are stored in off-heap and this tool only calculate on-heap size of objects referenced by

Re: Cache size in offheap mem in bytes

Hi, I have written a test program to find the cache size in bytes. I am using this tool (memory-measurer) to find the object sizes and its foot prints. I tried to use this tool to find the cache size in bytes. I am using on heap cache. Am I using

Re: Cache size in offheap mem in bytes

1) This applicable to Ignite. As it grown from GridGain sometimes it may appear in docs, because missed fro removal. 2) Yes, and I would say overhead could be even bigger. But anyway I cannot say definitely how much, because Ignite doesn't store data sequentially, there a lot of nuances. 3) Ignite

Re: Cache size in offheap mem in bytes

Hi, Thank you for the explanation. As per this link https://apacheignite.readme.io/docs/capacity-planning#section-calculating-memory-usage , "GridGain will typically add around 200 bytes overhead to each entry." 1) Why does it specifically say GridGain will add around 200 bytes overhead for

Cache size in offheap mem in bytes

Hi, an object takes 200 bytes on heap and cache has such 50 million objects stored in it. Is it ok to calculate cache size as follows? Cache size in bytes = object size * no of objects Cache size in bytes = 200 * 50 million Thanks, Prasad