Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <22366449.1157662763256.JavaMail.jira@brutus>
Date: Thu, 7 Sep 2006 13:59:23 -0700 (PDT)
From: "Rick Hillegas (JIRA)" <derby-dev@db.apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Updated: (DERBY-1664) Derby startup time is too slow
In-Reply-To: <32150767.1155233114573.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

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

Rick Hillegas updated DERBY-1664:
---------------------------------

          Urgency: Normal  (was: Urgent)
    Fix Version/s: 10.3.0.0
                       (was: 10.2.1.0)

Unassigning from 10.2. As far as I know this is not a regression.  I think this issue should not block 10.2.

> 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
>             Fix For: 10.3.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