Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Received-SPF: pass (asf.osuosl.org: local policy)
Date: Thu, 10 Aug 2006 11:23:44 -0700
From: David Van Couvering <David.Vancouvering@Sun.COM>
Subject: Re: [jira] Commented: (DERBY-1664) Derby startup time is too slow
In-reply-to: <10165411.1155233595306.JavaMail.jira@brutus>
Sender: David.Vancouvering@Sun.COM
To: derby-dev@db.apache.org
Message-id: <44DB79B0.5060507@sun.com>
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=UTF-8
Content-transfer-encoding: 7BIT
References: <10165411.1155233595306.JavaMail.jira@brutus>
User-Agent: Thunderbird 1.5.0.2 (X11/20060427)

I recognize this bug is too vague, but I wanted to get something into 
the system so we can start investigating it.  If I knew what "fast 
enough" was, then perhaps we could have a measure to close it.

If you were to ask me, "fast enough" is no more than 3 seconds with the 
default configuration.  5 seconds is pushing it.  What do others think?

 From a user's perspective it's irrelevant what component is causing the 
delay, it just takes too long (e.g. when I run 'connect 
jdbc:derby:mydb;create=true').

Also you of course need to describe the hardware configuration.  It all 
gets so nitpicky, when what we're after is fixing a perception.  Maybe 
it can be created as a project on the Wiki with a series of JIRAs 
attached to it?

David

Daniel John Debrunner (JIRA) wrote:
>     [ 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: 10.2.0.0
>>
>>
>> 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
>