The short answer is that it's complicated. You're probably better off creating some performance tests for your application and testing them out on the various options. Since the answers will vary depending on how your application uses the DB. For database applications I would recommend you pick the provider that supplies SSD storage.
The longer answer is that H2 is composed of multiple layers. The lowest layer is single-threaded, but the layers and caches above that are multi-threaded, and since a lot of queries spend a lot of time processing data, rather than reading/writing to the disk, we actually get a fair amount of parallelism out of our architecture. -- 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 h2-database+unsubscr...@googlegroups.com. To post to this group, send email to h2-database@googlegroups.com. Visit this group at http://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/groups/opt_out.
