Are you perhaps limiting the the size of the virtual machines memory with the -mX parameter?
This sounds like some kind of hitting-the-wall problem. On Sat, Jan 7, 2012 at 04:41, gonfi <[email protected]> wrote: > it was a fresh data import, no updates at all. > > > On Jan 5, 8:06 pm, Thomas Mueller <[email protected]> > wrote: >> Hi, >> >> I can't reproduce the problem with my test case. Maybe the database is >> fragmented? To defragment, run "shutdown defrag". >> >> Currently, H2 doesn't use server side cursors, which slows down queries >> with many rows (actually quite a lot, maybe 4 times). Server side cursors >> would help, and they are on the top of the priority list now, but this >> feature isn't available yet. >> >> Regards, >> Thomas > > -- > 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. > -- 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.
