db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel John Debrunner (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-1664) Derby startup time is too slow
Date Thu, 10 Aug 2006 18:13:15 GMT
    [ http://issues.apache.org/jira/browse/DERBY-1664?page=comments#action_12427303 ] 
Daniel John Debrunner commented on DERBY-1664:

Might be good to separate this out into:

1) driver load time
2) database create time
3) database open time
4) create table (first SQL command?) time

Also bugs like this tend to be problematic, when exactly does one close them. Better to identify
specific improvements that can be made and address those.

> Derby startup time is too slow
> ------------------------------
>                 Key: DERBY-1664
>                 URL: http://issues.apache.org/jira/browse/DERBY-1664
>             Project: Derby
>          Issue Type: Bug
>          Components: Store
>            Reporter: David Van Couvering
>             Fix For:
> 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


View raw message