You are could try playing with cache settings, that might help mask some of the
latency.
On 2014-07-08 12:45 PM, Tomasz Chmielewski wrote:
Thank you Noel. This is what I suspected, but hoped there is some way to fix it
or make it more stable.
On Tuesday, July 8, 2014 8:37:08 AM UTC+2, Noel Grandin wrote:
On 2014-07-05 08:22 PM, Tomasz Chmielewski wrote:
> I'm using eclipse PDT, which uses H2 DB for indexing data. there are
problems with accesing db - indexing a
single file
> takes ages, and it makes using eclipse literally impossible.
The exceptions are not serious, they are from a background thread. I
believe we have fixed this bug already.
>
> I run eclipse on windows 7, my workspace is a mapped network drive,
sources are located on debian machine, shared
> through samba, and that's where the h2 *.db files are located.
> Any clues what could be wrong or how to fix this? thanks in advance.
This is your problem - network drives are notorious for having highly
variable latency, which can play havoc with
database performance.
--
You received this message because you are subscribed to the Google Groups "H2
Database" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
[email protected]
<mailto:[email protected]>.
To post to this group, send email to [email protected]
<mailto:[email protected]>.
Visit this group at http://groups.google.com/group/h2-database.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "H2
Database" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/h2-database.
For more options, visit https://groups.google.com/d/optout.
