Hi, thanks for some more info. About performance I've came from some opinions here in google group and in H2 website. But I do no have yet direct comparsion. But, when I have some idle time(if ever) i'll do some comparsion on my database (cca 60 tables) and mix about 500 SQL which we use in our app and post result here.
Sincerely Petr Holik Dne čtvrtek 20. října 2016 9:49:19 UTC+2 Steve McLeod napsal(a): > > A good summary. Let me add some more info. > > * 1.4 can be used for production same as 1.3 when >> ;MV_STORE=FALSE;MVCC=FALSE is appended to JDBC URL (MVCC is now >> disabled when not using MV_STORE - so potetionally can be omited) >> > > Appending ;MV_STORE=FALSE to the JDBC URL is enough to use the PageStore > (the solid, reliable. database storage mechanism used in H2 1.3. You do > mention this, but let's make it explicit! > > >> * MV_STORE should now have pretty similar performance as old one >> > > I disagree. In my own performance tests, the MV_STORE (as of H2 1.4.192) > becomes much slower on a large database (say, > 1 GB) with many SQL UPDATE > statements. > > > -- 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 https://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
