Hi Sylvain, We have returned to the library we used previously: MapDB. http://www.mapdb.org/
MVStore was significantly faster in our case regarding write operations. Still we could not live with the progressively growing storage file. I think our scenario is not optimal for MVStore. We store ~10,000 structures of size ~170kB which are modified quite frequently. MVStore afaik puts the modified blocks to disk while keeping the original ones, as well. This model is for allowing versioning and rolling back to previous versions. This model also accounts for fast write operations. This model unfortunately also accounts for the enlarged storage file in our case. We do not need versioning at all but still this feature can not be switched off, as it is part of the storage concept. Hope this helps, Regards, Roland On Thursday, July 6, 2017 at 8:35:36 PM UTC+2, epsilon68 wrote: > > >> Unfortunately, we have replaced MVStore in our project as we could not >> handle the database file size growth problem even using compactMoveChunks() >> method. >> > >> Please could you share a bit more? which library did you use instead? > what is your feedback on the H2's replacement? > -- 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.
