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 each entry? Does ignite not add this overhead? 3) Does this <https://apacheignite.readme.io/docs/capacity-planning#section-memory-capacity-planning-example> example already considers 200 bytes overhead per entry? 4) When ignite transaction is started, it keeps the cache updates in temp cache or transactional cache and it is kept in on-heap. Does this rule apply to transactional cache as well? Regard, Prasad On Wed, Jun 27, 2018 at 2:15 PM dkarachentsev <dkarachent...@gridgain.com> wrote: > Hi, > > It will be incorrect, because entries are not stored sequentially, there > are > a lot of infrastructure that requires additional space. For example, memory > is divided into pages and each page has header, each entry has key and > value, version and other service information. For quick access to entries > is > created b+tree (which consists of pages too), synchronization primitives, > links and binary object overhead to allow access to it's fields. > > It's quire hard to say how much memory will be required, just approximately > [1]. The best way will be to load some number of data and measure how much > memory was consumed. You need to make many such measures, because only on > large number of entries memory consumption will increase linearly. > > [1] https://apacheignite.readme.io/docs/capacity-planning > > Thanks! > -Dmitry > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
