Hi, I downloaded the latest stable release from the website this morning. I have setup an in-memory database with the url jdbc:h2:mem and created a single table with 50k rows in it. I create the table with a primary key, add 2 indexes, load the data and then run analyze. I have checked the queries and plan indicates to use the indices roughly correctly.
When I query the data to return 2100 rows it takes 300 mSec. If I query to return 12 rows it also takes around 300 mSec. This is on a recent HP multicore machine with 3GB ram (total JVM size is around 80-128MB), no other significant activity on the machine. I can also put the database on disk, jdbc:h2:~/test and do the queries. They take about the same amount of time, perhaps a little less. On disk the database is about 11M and the indices about 8MB. My question is, out of the box what do I need to do to make the in- memory mode perform well. Are there settings for the size of the database, besides the JVM settings. Are there any conditions when H2 will try and spool data out to the disk even though the database is in memory? Thanks --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
