On 5/4/06, Lachlan Deck <lachla..sh.com.au> wrote:
> I've been testing an initial population of a Derby database with some
> 30-40000 records and am finding a large performance difference
> between using the EmbeddedDriver vs the ClientDriver i.e., depending
> on whether Derby is run as an embedded or network service for the
> application.
>
> Using the Embedded driver seems to take an order of magnitude longer
> than not (e.g., 2-3 hours vs 15 minutes)!
There's lots of possibilities. One that comes to mind is that your
embedded database may be hitting a maximum memory size and spending
all of its time swapping/garbage collecting.
I've seen this happen with an embedded HSQLDB database.
This archive was generated by hypermail 2.0.0 : Thu May 04 2006 - 20:47:33 EDT