[following up on my own post] On Sunday, December 9, 2018 at 4:59:50 PM UTC+10:30, Matthew Phillips wrote:
I was just about to ask if it would make sense to provide an interface that > can be optionally implemented by clients to estimate the size of an object, > but it just hit me that I may have made an incorrect assumption about > DataType.getMemory: I assumed it is the serialised size of the object, but > is it? Is getMemory actually what I want here? > Looking through the code in MVMap and Page, it seems getMemory() is indeed for estimating heap size, not serialised size. Wow. I made a bad assumption, thinking of DataType as only about pluggable serialisation. I'll go back and rewrite getMemory() to be for heap size, and see how it goes (I'm using Clojure persistent collections which obviously need a custom implementation). BTW after several days of operation, the MVStore from git master hit a corrupted store error, which I'll file as an issue. -- 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.
