We are using H2 as an embedded POS database (it have been very fast and very stable, thanks!)
One issue I am trying to solve is caused by updates to items and prices being loaded while the the register is being used during the business day. Does anybody have recommendations on how to best accomplish concurrent read and update/insert access to the database? 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? Is MVCC stable enough for production usage? What does setting MULTI_THREADED=1 accomplish? I can't glean from the documentation what MULTI_THREADED will buy us. 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? Thanks in advance for any help that can be provided! --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
