Hi Jan. Just out of interest... Is there an index on table.s1 and more importantly, how much memory did you allocate for the database to use as cache ? This can have a tremendous impact. On own of my databases just increasing the memory to 32mb from 16mb caused a 3 second query to become a sub-second query.
Best regards Ewald On Mar 1, 9:05 pm, Jan Kotek <[email protected]> wrote: > Hi, > > I took H2 for quick spin on table with 1e6 records on disk. It was dog > slow on queries like > "SELECT * FROM table WHERE table.s1 LIKE 'Peter' > > Is H2 designed to handle this amount of data? Or I am doing something > wrong? > > I also took look into source code. I found two major problems: > > 1) Does one node in BTree consumes one page in storage?! This would > explain slow performance on btrees indexes. > > 2) Each read is synchronized on Storage. So DB can not fetch multiple > pages/columns from disk at one time. > > Are there any plans about rewriting indexes and storage generally? > > Thanks, > Jan Kotek --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
