[
https://issues.apache.org/jira/browse/DERBY-1664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Hillegas updated DERBY-1664:
---------------------------------
Attachment: derby_1664.java
Attaching a new version of the test, incorporating the following changes:
o Cleaned up the output script. Now there is only one attempt to connect to the
results database and create a schema. The generated script should run without
any errors.
o Added another argument to the test: the boot instant. This allows the test to
calculate how long it takes to fault in the VM.
Here's a revised script for running the test:
rm derby_1664.sql
for counter in 0 1 2 3 4 5 6 7 8 9
do
echo Run number $counter...
export bootInstant=`java 'derby_1664\$CurrentTime'`
java derby_1664 $bootInstant $counter memory 10
export bootInstant=`java 'derby_1664\$CurrentTime'`
java derby_1664 $bootInstant $counter disk 10
done
I ran the test against 3 versions of Derby which support in-memory databases:
10.5.1.1, 10.6.1.0, and the 10.7 trunk. For all three versions on my reasonably
peppy machine I saw the following:
1) It took a little less than a second to boot the VM and fault-in the Derby
driver.
2) Creating the first database took another second.
3) Creating subsequent on-disk databases took a half second apiece.
4) Creating subsequent in-memory databases took a quarter second apiece.
Here are the results of my test runs:
################################################
10.5.1.1:
CONFIGURA&|VMBOOT |DRIVERLOAD |DBCREATE
|DBCLOSE |REOPEN |TABLECREATE
----------------------------------------------------------------------------------------------------------------------------------------
DISK |327 |412 |958 |14
|49 |168
MEMORY |337 |459 |762 |8
|13 |162
CONFIGURA&|VMBOOT |DRIVERLOAD |DBCREATE
|DBCLOSE |REOPEN |TABLECREATE
----------------------------------------------------------------------------------------------------------------------------------------
DISK |0 |0 |439 |10
|24 |19
MEMORY |0 |0 |228 |4
|11 |9
################################################
10.6.1.0:
CONFIGURA&|VMBOOT |DRIVERLOAD |DBCREATE
|DBCLOSE |REOPEN |TABLECREATE
----------------------------------------------------------------------------------------------------------------------------------------
DISK |323 |436 |1196 |16
|26 |175
MEMORY |333 |482 |915 |9
|14 |170
CONFIGURA&|VMBOOT |DRIVERLOAD |DBCREATE
|DBCLOSE |REOPEN |TABLECREATE
----------------------------------------------------------------------------------------------------------------------------------------
DISK |0 |0 |491 |13
|23 |15
MEMORY |0 |0 |253 |5
|12 |7
################################################
10.7 trunk:
CONFIGURA&|VMBOOT |DRIVERLOAD |DBCREATE
|DBCLOSE |REOPEN |TABLECREATE
----------------------------------------------------------------------------------------------------------------------------------------
DISK |325 |439 |1149 |18
|28 |176
MEMORY |327 |438 |953 |9
|14 |172
CONFIGURA&|VMBOOT |DRIVERLOAD |DBCREATE
|DBCLOSE |REOPEN |TABLECREATE
----------------------------------------------------------------------------------------------------------------------------------------
DISK |0 |0 |499 |13
|23 |15
MEMORY |0 |0 |263 |5
|16 |7
> 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, 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.
