Is it CPU bound or disk bound during that 90 seconds when the query is
running?
You can try increasing JVM memory?
The the slow query the same as all the others?. perhaps it isn't using
an index for that query?
You really need to try and find out what is going on, or get it running
in a tes
On Wednesday, September 17, 2014 12:14:32 AM UTC+5:30, Thomas Mueller wrote:
>
> Hi,
>
>>
>> and jar version is h2-1.1.114.jar.
>>
>
> Hm, that's very very old. Could you upgrade to a more recent version?
>
> jdbc:h2:/data/Testbed/h2DB/Arun;DB_CLOSE_ON_EXIT=FALSE;FILE_LOCK=NO;LOG=2
>>
>
> I hope
Hi,
>
> and jar version is h2-1.1.114.jar.
>
Hm, that's very very old. Could you upgrade to a more recent version?
jdbc:h2:/data/Testbed/h2DB/Arun;DB_CLOSE_ON_EXIT=FALSE;FILE_LOCK=NO;LOG=2
>
I hope you understand that FILE_LOCK=NO is very dangerous.
Regards,
Thomas
--
You received this messa
Hi guys..
I am new in H2DB .i m running system where H2db is having around 3 crore
[30 million] data in one table only. [H2DB contains 1 table only]
select query normally takes milliseconds only.around 100-200 ms.
bt at sudden h2db takes upto 90 second for a single fetch query.
this happens fo
