db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-1664) Derby startup time is too slow
Date Wed, 08 Sep 2010 09:47:34 GMT

    [ https://issues.apache.org/jira/browse/DERBY-1664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12907146#action_12907146
] 

Knut Anders Hatlen commented on DERBY-1664:
-------------------------------------------

I ran the tests on my workstation (running Solaris 11 Express snv_147), and got these results
(averaged over 10 runs):

Java 1.6.0_21:

CONFIGURA&|DRIVERLOAD          |DBCREATE            |DBCLOSE             |REOPEN     
        |TABLECREATE         
-------------------------------------------------------------------------------------------------------------------
DISK      |231                 |801                 |8                   |11             
    |117                 
MEMORY    |231                 |675                 |6                   |8              
    |111                 

CONFIGURA&|DRIVERLOAD          |DBCREATE            |DBCLOSE             |REOPEN     
        |TABLECREATE         
-------------------------------------------------------------------------------------------------------------------
DISK      |0                   |253                 |4                   |10             
    |9                   
MEMORY    |0                   |153                 |2                   |5              
    |4                   

Java 1.7.0-ea-b108:

CONFIGURA&|DRIVERLOAD          |DBCREATE            |DBCLOSE             |REOPEN     
        |TABLECREATE         
-------------------------------------------------------------------------------------------------------------------
DISK      |250                 |745                 |8                   |11             
    |129                 
MEMORY    |250                 |660                 |6                   |8              
    |138                 

CONFIGURA&|DRIVERLOAD          |DBCREATE            |DBCLOSE             |REOPEN     
        |TABLECREATE         
-------------------------------------------------------------------------------------------------------------------
DISK      |0                   |247                 |4                   |8              
    |8                   
MEMORY    |0                   |145                 |2                   |5              
    |4                   

So in my experiments there was no difference in DRIVERLOAD between memory and disk databases,
as one would expect.

> Derby startup time is too slow
> ------------------------------
>
>                 Key: DERBY-1664
>                 URL: https://issues.apache.org/jira/browse/DERBY-1664
>             Project: Derby
>          Issue Type: Improvement
>          Components: Store
>            Reporter: David Van Couvering
>         Attachments: derby_1664.java, 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.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message