Andrey, How good will be the estimate if we go for 1. and utilize pagesFillFactor somehow? In other words, how big can be a difference between 100% precise calculation you the approach you're suggesting?
-- Denis On Thu, Mar 22, 2018 at 11:17 AM, Andrey Kuznetsov <stku...@gmail.com> wrote: > Denis, > > Do we really need to measure cache sizes precisely? We can use approach 1 > and also we have average pagesFillFactor metric. These two metrics can give > a good estimation of page memory size per cache. > > 2018-03-22 21:04 GMT+03:00 Denis Magda <dma...@apache.org>: > > > Igniters, > > > > Glad to see that 2.4 made it possible to show memory usage in bytes for > > data regions. Good progress but it's definitely not enough. > > > > I'd like to discuss how we can support "memory usage per cache/table" in > > bytes. That's actually what the users are interested in. Talking to Alex > G. > > we came up with 2 possible approaches: > > > > 1. Usage of a per cache counter that accumulates total size of all binary > > objects passed through our cache update/insert/remove API. Pros: easy to > > implement. Cons: we don't consider extra space taken by our data pages > and > > other memory components. > > > > 2. To address the cons of 1. we can count the size of the data pages, but > > in that scenario, a data page must not store entries of varies cache. > This > > approach is ideal for the memory usage by cache reporting but requires > more > > changes in the architecture side. > > > > Alex G., please step in and give more details suggesting your approach. > > > > Others, please join the discussion as well. > > > > -- > > Denis > > > > > > -- > Best regards, > Andrey Kuznetsov. >
