This brings up an interesting idea. Perhaps the engine could notify the user if resources are too low? If memory allocation is too small to cache all the data/indexes, the engine could alert the user and maybe link them to the part of the manual describing how to increase cache size.
What do you think Thomas? -Evan On Feb 23, 2:20 am, Ewald <[email protected]> wrote: > Hello fellow newbies. > > I've recently run into a situation where my SQL query results were > ridiculously slow all of a sudden as my table entries reached 50000 > records. After rebuilding indexes and trying all sorts of other silly > ideas, I happened to check the memory use of H2 database : a whole > 32mb. Mmmmm, funny, since the MySQL instance I used before helped > itself to quite a bit more memory. > > It got me thinking that maybe there are some settings I should change > to optimize H2 a little bit. After a quick study of the documentation > I found exactly what I was looking for : > > set cache_size XXXXX > > After allocating a little bit more memory (a modest 64mb instead of > the very modest default 16mb) my queries were blazing fast again! > > And of course, once more H2 kicks dust in the face of competitors. > > The moral is of course to ensure that you allocate enough resources to > H2 to enable it to do it's job effectively. > > Have fun with H2. > > Regards > Ewald --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
