On Jun 6, 5:46 am, Thomas Mueller <[email protected]> wrote: > Hi, > > > I tried turning on MVCC mode, but it slows down our initial data loads > > by a factor of 4-5. It would be acceptable to take the performance > > hit after an initial data load has completed. Can MVCC mode be turned > > on dynamically? > > To turn it on or off, you need to close the database. > > > Is MVCC stable enough for production usage? > > That's hard to say. It it not used as much as the regular mode. > > > What does setting MULTI_THREADED=1 accomplish? I can't glean from the > > documentation what MULTI_THREADED will buy us. > > It is useful if you have a few long running queries (read-only), while > at the same time quick queries. It can not be combined with MVCC at > the moment. This feature is less tested than MVCC. The total > throughput will decrease. It doesn't help much if you have large write > operations. > > > Note that our background item/price loads can (currently) happen in > > fairly large transactions. > > Maybe my best option would be to just > > ensure that transactional updates are broken up into smaller > > transactions and make sure that the LOCK_TIMEOUT is set high enough to > > allow reads to slip in during loads? > > Yes, I believe that would be the best solution.
Thx. That's the path we headed down. > > Regards, > Thomas --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "H2 Database" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/h2-database?hl=en -~----------~----~----~----~------~----~------~--~---
