[ http://issues.apache.org/jira/browse/DERBY-1664?page=all ]

David Van Couvering updated DERBY-1664:
---------------------------------------

    Attachment: perftest.diff

I am attaching a set of unit tests I built to time the various parts of 
startup.  On my Solaris x86 with the write cache enabled (my research shows it 
can't be *disabled* with IDE drives) I have quite acceptable startup times, 
with the majority of it being spent on database creation.

Next week I'll try some runs on a Linux machine whose SCSI drive has the write 
cache disabled.  I wonder if people who are having trouble are running in such 
environments...

If these tests look good, I can check them in.

.Testing startup with a NEW database... All measurements are in milliseconds.
Loading driver:  371
Open connection with creating new database:  1212
Creating a table:  232

Time: 1.817

OK (1 test)

.Testing startup with an EXISTING database... All measurements are in 
milliseconds.
Loading driver:  302
Open connection with existing database:  353
Creating a table:  286

Time: 1.22

OK (1 test)


> Derby startup time is too slow
> ------------------------------
>
>                 Key: DERBY-1664
>                 URL: http://issues.apache.org/jira/browse/DERBY-1664
>             Project: Derby
>          Issue Type: Improvement
>          Components: Store
>            Reporter: David Van Couvering
>         Assigned To: David Van Couvering
>             Fix For: 10.2.0.0
>
>         Attachments: perftest.diff
>
>
> I know it's hard to measure what "too slow" is, but this is a common 
> complaint and this affects overall perception of Derby.  This appears to be 
> related to another common complaint that it takes too long to create tables.  
> I am marking this as Urgent because of the impact it has to Derby perception 
> and the fact that the 10.2 release is going to get such wide distribution 
> through the Sun JDK.
> For background, see http://www.nabble.com/Startup-time-tf2012748.html#a5531684

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to