Hi there,
On 05/05/2006, at 10:43 AM, Jean T. Anderson wrote:
Lachlan Deck 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)!
fascinating. Normally the embedded driver is faster.
So I've read.
Which client JDBC driver are you using?
For embedded Derby: org.apache.derby.jdbc.EmbeddedDriver
For network Derby: org.apache.derby.jdbc.ClientDriver
Both are using the adaptor:
org.objectstyle.cayenne.dba.derby.DerbyAdapter
Which specific version of Derby are you running? Can you post the
output from:
I've tried both the lastest stable and recent nightly build. No
difference.
java org.apache.derby.tools.sysinfo
$ java -cp "<..>lib/derby.jar" org.apache.derby.tools.sysinfo
------------------ Java Information ------------------
Java Version: 1.5.0_06
Java Vendor: Apple Computer, Inc.
Java home: /System/Library/Frameworks/JavaVM.framework/Versions/
1.5.0/Home
Java classpath: "<..>lib/derby.jar:/System/Library/Frameworks/
JavaVM.framework/Versions/1.5.0/Classes/.compatibility/
14compatibility.jar
OS name: Mac OS X
OS architecture: ppc
OS version: 10.4.6
Java user name: lachlan
Java user home: /Users/lachlan
Java user dir: /Users/lachlan
java.specification.name: Java Platform API Specification
java.specification.version: 1.5
--------- Derby Information --------
JRE - JDBC: J2SE 5.0 - JDBC 3.0
[<...>lib/derby.jar] 10.1.2.1 - (330608)
------------------------------------------------------
----------------- Locale Information -----------------
------------------------------------------------------
lachlans-imac:~ lachlan$
Lachlan Deck
[EMAIL PROTECTED]
+61 2 9550 5001
