Noel, As always, thanks for your insights. It is good to know that H2 at its cores is single threaded while at the same time multithreaded at outer layers. , this will help me as I think about my design. SSD is a good option, looking to use Digital Ocean https://www.digitalocean.com/. Good SSD, but it only scales CPU via more cores not time slices (as opposed to http://www.linode.com) I have a hunch this mutli core scaling is not the best option for H2. But overall seems like nice service, and my hunches are often times wrong :) -Adam
On Sunday, November 10, 2013 4:16:28 AM UTC-5, Noel Grandin wrote: > 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 [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/groups/opt_out.
