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
