Re: [h2] MVStore caching on read

2017-03-15 Thread Roland Lohner
Hi Thomas, I suspect you misunderstood case B). In that case only the search function is called. It means there is no overwrite as there are no put operations, only get operations are called. I am wondering what causes the different used cache size in case B) Regarding 1.7G java memory vs. 5G

Re: [h2] MVStore caching on read

2017-03-15 Thread Thomas Mueller Graf
Hi, OK I see. I'm not sure, maybe this is a bug? Can you reproduce it with a simple test case (for example using )? Regards, Thomas On Wed, Mar 15, 2017 at 12:20 PM, Roland Lohner wrote: > Hi Thomas, > > I suspect you misunderstood case B). > In that case only the search function is called. >