First off thanks Thomas for all the great work - after switching from Derby to H2 everything runs twice as fast!
Still I find that we are limited by insert performance. I wrote up a small test to insert 100,000 rows and found - with single thread and single table - 11,000 rows per second with 8 threads and single table - 14,000 rows per second with 8 threads and 8 tables - 14,000 rows per second Tests were done on an 8 core Linux server with an embedded in-memory database. With the multi thread tests CPU usage was around 30%-40% per for each core. The db url is jdbc:h2:mem:testdb. My biggest surprise was that the 8 table test was no faster. I would expect with no contention for table locks this would scale better. Is there any recommended configuration to allow better insert performance? Thanks, Greg --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "H2 Database" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/h2-database?hl=en -~----------~----~----~----~------~----~------~--~---
