I analyzed contention several times and now again, didn't notice any lock contention between the threads or processes. I don't think there's a global state as the module does not depend on anything external, it is very much self contained. The only shared thing here is the H2 TCP port which is randomly chosen during the build and the TCP server fails if it is already taken.
Regarding your suggestion on removing the TCP connection - I will try that, along with experimenting with the optional nioMemFS file system module to see if there are any performance differences. It will take me some time to perform these experiments as each round takes about an hour and a half. Thanks again! On Monday, May 1, 2017 at 12:35:51 PM UTC+3, Noel Grandin wrote: > > Does VisualVM perhaps show some high contention on any locks? > > Perhaps there is some global state which is accidentally causing problems? > > Since you are running in embedded mode, perhaps use H2 with a URL like > this: > jdbc:h2:/path/to/db;USER=<user>;PASSWORD=<password>;... > and skip the tcp connection > ? > -- 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.
