We are testing the latest H2 version (from a recent nightly build, actually) in place of a rather ancient but serviceable version 1.2. We are seeing performance degradation of at least a factor of 6. We have suites of test. I can supply you with comparison timings, but for example a suite that takes 20 minutes on the old H2 is timing out after 3 hours. If we don't need MVCC for a suite, we could run it without it. Will that recover the lost time? (That's an experiment I will run later.) We want to take advantage of MVCC (and DBStore) for some integration suites where we hope it will prevent deadlocks. Let me know if you need more details, or if you can respond with general comments about expected performance.
-- 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.
