Since it happens with both imdb and h2, it is most likely a bug in your code
On Monday, 12 December 2011, Vinod <[email protected]> wrote: > I wonder why nobody else has faced this issue or nobody has compared > the inMemory vs nonInMemory performance. > > > On Dec 8, 10:48 am, Vinod <[email protected]> wrote: >> The total number of records is 1055. >> I tried it with following xmx settings: -Xms1024m -Xmx2048m >> Still the time taken to execute query in memory is 1500ms >> On Dec 8, 8:02 am, andreis <[email protected]> wrote: >> >> >> >> >> >> >> >> > > - when run in memory - 1500ms >> > > - when not run in memory - 426ms >> >> > Due to Garbage Collector? Try setting -Xmx high enough to hold all >> > that data in memory. > > -- > 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.
