Yes, we're opening/closing the database connection a lot. I'm not sure how easy it would be for us to change that.
A mechanism to disable the fsync calls would be appreciated -- people grumble about our tests taking 7 mins, so there's no way I'm upgrading to 131 and a 12 minute test run :-( Thanks Kerry On Tue, Mar 23, 2010 at 9:06 AM, Thomas Mueller < [email protected]> wrote: > Hi, > > > 131 ... our tests now take around > > 12 mins, vs the 7 mins in 127. > > The H2 unit test s are now also slower. The main reason is most likely > that when closing the database, and on checkpoint, H2 now calls > FileDescriptor.fsync(). Other databases call it for each commit by > default, see also > http://www.h2database.com/html/advanced.html#durability_problems > > I did enable fsync because it reduces the probability of corrupted > databases in the power failure test. But I'm not sure if it will > actually solve the problem in each case. My plan is to regularly run > power failure tests from now on to find out (they are running > currently). > > Anyway, if your test closes the database a lot (the H2 built-in tests > do), or if you use a small log size, it will be slower. If not, then > it shouldn't matter that much. If it does, maybe I should add a way to > disable calling fsync. > > 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]<h2-database%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/h2-database?hl=en. > > -- 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.
