Hello, we've been having great success with MVStore (1.4.197) as a KV-store backing our sync service. But we're seeing excess RAM usage for some of our servers, and it turns out to be in the MVStore cache.
Using JVisualVM to analyse a heap dump of live objects from an affected server, I can see the total retained size of the MVStore cache is ~345MB, for a store configured with 96MB of cache. cache=org.h2.mvstore.cache.CacheLongKeyLIRS#1 345,771,938 B (85.9%) As an example, one of the biggest segments is using ~18MB: [12]=org.h2.mvstore.cache.CacheLongKeyLIRS$Segment#30 17,952,945 B (4.5%) But the segment thinks: maxMemory = 6,291,456 usedMemory = 5,342,814 I realise from reading previous discussions here about MVStore caching that size estimation is in inexact science, but I'd really like find out why it's getting it so wrong here (and fix it). Can anyone offer some advice on what may be wrong and how to proceed? Cheers, Matthew. -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
