On 2017/01/11 2:10 PM, Bernd Schuller wrote:
as a secondary issue: the MVStore cachedChunkRef gets much bigger than the
limit, and is not cleaned up by garbage
collection.
What is the recommended way to handle this?
That would a bug, a patch to fix it would be best :-)
But are you sure about that, I have never seen that cache show up in my
profiler.
I noted that setting the cache size in MVStore via SET CACHE_SIZE only sets the memory
limit on "cache" and does not
influence the memory limit on the "cacheChunkRef". This means the cacheChunkRef
uses quite a bit of memory (4MB). Is
this intentional? Would it make sense to have SET CACHE_SIZE set memory limits
on both the caches?
Is 4M really that much memory? :-)
But anyhow, I would be happy to accept a patch that makes the cachedChunkRef cache limit itself to some multiple of the
SET CACHE_SIZE setting.
--
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.
