One thing that is not always understood is how low the default cache size is for most applications that are beyond toy size.
At least that was true a year ago. Our app dedicates 1/5 of available memory to H2 cache; this is larger than most people need but we have a server app and can afford it. But I would test your case with the cache size set to 64m, 128m etc. There is a section in the faq or in the features page regarding cache size. It has a big impact on certain kinds of queries in terms of performance. C > > In this case, H2 does not use the index for ordering. > So as a consequence, it has to order the whole resultset, before it > can return anything, i.e. the initial query will always be slow. > > The only think I can think of that might speed up the thing is > tweaking some memory settings to make sure everything is ordered in > memory. > > So, for resultsets up to 200.000, but usually between 10.000 and > 50.000, is there a recommended setting to speed up ordering in memory? > > Thanks, > > -hendrik > > > > -- C. Schanck --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
