I just wanted to chime in with a performance issue that may be related to tsukasa's problem...
I recently looked at upgrading to a new version of H2 for our project's tests and discovered that something has caused performance issues between 1.2.127 (which was fast) and 1.2.131 (which is much slower). 127 was good, and fast. Running all our tests took about 7 mins. 128 changed behaviour which meant that one of our unit tests failed, when it clearly shouldn't. 129 was broken for us with the "parent not found" error 130 was broken for us with the "table not found" error 131 wasn't broken, and all our tests passed, but our tests now take around 12 mins, vs the 7 mins in 127. We have over 750 tests, so it's a bit hard to come up with a reproducable test case. Cheers Kerry On Tue, Mar 23, 2010 at 12:49 AM, [email protected] <[email protected]>wrote: > > On Mar 22, 1:32 pm, tsukasa <[email protected]> wrote: > > I guess would be good if you report use cases when the new format is > > still that much slower. > > I outlined my use case: embedded mode. A lot of inserts and updates. > There are about 3 main tables with referential integrity between them. > Oh, and there are blobs. Each record has one. > > Thanks, > Zviki > > -- > 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.
