The thing is, I don't think there is a problem. I think that your code is not caching PreparedStatement 's properly, and the rest of H2 is so fast, that the only thing left in the profile is the parser initialisation :)
On Wed, 05 Aug 2015 at 16:27, Steve McLeod <[email protected]> wrote: > Hi Noel, > > I've actually solved this problem of PreparedStatement caching for my app > by increasing QUERY_CACHE_SIZE to 100. But I'm interested in helping solve > the bigger issue of why it seems to take a comparatively significant time > to create a PreparedStatement. > > Cheers, > > Steve > > > On Wednesday, 5 August 2015 16:04:46 UTC+2, Noel Grandin wrote: >> >> >> Thanks, I'll have a look tomorrow at them in detail. >> >> Tell me, how often is JdbcConnection@preparedStatement called compared >> to how many times you execute a query? >> >> If it's every time, it means that your PreparedStatement caching is not >> working, which would indicate a problem with >> your connection pool, or something similar. >> >> -- > 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 http://groups.google.com/group/h2-database. > For more options, visit https://groups.google.com/d/optout. > -- 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 http://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
