On Saturday, 22 July 2017 03:59:42 UTC-4, Noel Grandin wrote: > > what does your H2 URL look like? Are you using the H2 JDBC driver? > > If your app is heavily multi-threaded, you could try MULTI_THREADED=true, > which is almost production-ready >
I've tried the following: 1) jdbc:h2:tcp://localhost:50000//path/to/mydb;DB_CLOSE_DELAY=-1 2) jdbc:h2:tcp://localhost:50000/mem:mydb;DB_CLOSE_DELAY=-1; 3) jdbc:h2:mem:mydb;DB_CLOSE_DELAY=-1 #2 made a measurable improvement, which is where I am now with average latency being 100x longer, but from there trying embedded didn't help. Also tried MULTI_THREADED=1 which didn't help. -- 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.
