On 2014-10-08 01:52 AM, b g wrote:
    As a follow up,

I unit tested mutli-threaded inserts, reads and updates up to 100000 entries 
and have seen awesome performance, lets say
under 8 msecs average while on a taxed VM - I did a simple unit test with a 
loop that drops runnables into the thread
executor. But, when I mix inserts and reads... it falls apart quickly.

I've read the performance tuning page - not much about multi-threading....  can 
someone comment on some experiences with
doing high concurrency with H2? My application reads from multiple JMS 
queues/topics - each on its own thread, then
dumps it to the H2 DB. Other threads grab the messages and "process" them - we 
are seeing 1+ second read times when
under "light" loads. I am using connection pooling with the apache 
BasicDataSource - using the default - Im concerned
because I see threads in the BLOCKED state from inside the H2 DB Drivers.



I would start by batching your inserts and reads.

Also you might want to try running the latest 1.4 version (but with MV_STORE turned off) because we made some fixes there that might help prevent the kind of 1+ second read times you are seeing.

--
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/d/optout.

Reply via email to