Hi, I'm trying MVStore to implement a change tracking feature in a large
graph structure, using several MVMaps with custom data types. In a recent
test, I had a load like this:
Opened new store, added ~1M entries, with roughly 10Byte serialized data
each, closed. MVStore file size was ~1.6 GB
Store version was ~750, obviously the number of autocommits that happened.
Keys have a near to random distribution.
In my case, some latest versions are useful to realize n concurrent readers
with 1 writer. Most old versions could be discarded. I mean, 1.6GB is
little large when, ideally, just ~10MB would do. Can you give me some
advice? Is there an option to discard old versions? Can I optimize chunk
sizes, and what are the criteria? Play with autocommit frequency?
Using version 1.3.175
--
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 h2-database+unsubscr...@googlegroups.com.
To post to this group, send email to h2-database@googlegroups.com.
Visit this group at http://groups.google.com/group/h2-database.
For more options, visit https://groups.google.com/d/optout.