Hi,

I'd like to use the embedded version of the H2 Database with OBD on
cloud services to create a high performance web service. The web
server only performs selects but each request generates 15-20 database
queries. I've set the H2 database to read only so that it resides in
memory and the DB itself is not that large -- about 20 MB.

Does anyone have experience with performance tuning H2? What settings
would you suggest? I have stuck to default settings:

Maximum Connections: 24
Connection Timeout: 120
Login Timeout: 120
Connection Retries 0

Is it true that H2 can only process one query at a time and that this
creates a backlog of queries? In practical terms does this really
limit performance versus the traditional set up using a standalone
database (e.g. mySQL) on a separate server?

The nice thing about using the H2 DB and OBD is that it's a very
simple and compact package and we can use to quickly spin up new
instances. I wonder if the trade-off in performance might be somewhat
compensated for by thte fact that we can just launched a few more
instances?

Anyway, would love to hear what the community thinks and what
experience / lessons you can share.

Thanks!
GT

-- 
Open BlueDragon Public Mailing List
 http://www.openbluedragon.org/   http://twitter.com/OpenBlueDragon
 mailing list - http://groups.google.com/group/openbd?hl=en

 !! save a network - please trim replies before posting !!

Reply via email to