On Mar 22, 3:28 pm, Kerry Sainsbury <[email protected]> wrote: > 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).
Sorry if this is a closed thread but quick searching through the archives seems like there wasn't a resolution here. I also recently upgraded from 1.1.106 to 1.2.134 and saw my unit tests go from 4.0 seconds to 28.5 seconds. I went through each of the releases and I see the following performance times across 463 unit tests in my ORMLite simple Java annotation based ORM package (http:// ormlite.sourceforge.net/). They are all testing ORM functionality so I need a fresh database each time. The database URL I am using is "jdbc:h2:mem:ormlite" so I don't think it is anything to do with fsync as previously mentioned. Each run I made a number of runs and averaged the times. 1.1.106 = 4.0 s 1.2.127 = 3.5 s 1.2.128 = 3.3 s 1.2.129 = 28.5 s For a comparison, here are some other Java database packages: derby disk 10.4.2.0 = 36 s hsqldb mem 1.8.0.10 = 29.7 s sqlite disk 3.6.20 = 36 s sqlite mem 3.6.20 = 27 s Looking carefully though the 1.2.129 ChangeLog entries, I don't see anything specifically which would indicate this issue. Is there some new setting that I am missing? My test sources are online (https://sourceforge.net/projects/ormlite/ files/) but I would be happy to try other H2 versions to help locate the source of this performance change if it is not already understood. thanks, gray -- 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.
