Hi Thanks for the excellent test case.
I note that most of the time is being spent in the planning phase of the query. I have just pushed a commit which makes 1.4 about twice as fast as it was before. You can build from source to try it out. It is, however, never going to be as fast as 1.3, because 1.4 tries a lot harder to build an optimal plan for queries. You should using PreparedStatement in your code to avoid running the planning phase often. You can also bump up the size of the H2 query cache if you have an unusually large number of independent queries. Either way, you should not be hitting this path often. Regards, Noel. -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
