Hi, > We are using MySQl's INNODB engine. In testing itself, for long > running query we face lot of issues with lock wait time out.
InnoDB uses row level locking, H2 without MVCC - table level, so in that case you probably will experience these problems even more. With MVCC H2 still does not scales very well because all update queries are running sequentially. But this all really depends on workload type and for your case H2 may work well enough. If your app is database agnostic then you should just test it with H2 and then decide. By the way lock wait timeout is a tunable parameter in both MySQL and H2 so may be you should just increase it. > But again concurrency with H2(with or with out MVCC and embedded or > server mode)?? There are two options in H2 for better cocurrency MVCC and MULTI_THREADED. Both has advantages and disadvantages (you can google some discussions in this group about this topic), better to test both. For maximum performance better to use embedded mode but this is not about concurrency. regards, Sergi -- 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.
