[jira] Updated: (DERBY-1664) Derby startup time is too slow

2010-09-09 Thread Rick Hillegas (JIRA)
[ 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 chan

[jira] Updated: (DERBY-1664) Derby startup time is too slow

2010-09-07 Thread Rick Hillegas (JIRA)
[ 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 derby_1664.java. This program uses System.currentTimeMillis

[jira] Updated: (DERBY-1664) Derby startup time is too slow

2006-09-07 Thread Rick Hillegas (JIRA)
[ 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

[jira] Updated: (DERBY-1664) Derby startup time is too slow

2006-08-11 Thread David Van Couvering (JIRA)
[ http://issues.apache.org/jira/browse/DERBY-1664?page=all ] David Van Couvering updated DERBY-1664: --- Attachment: perftest.diff I am attaching a set of unit tests I built to time the various parts of startup. On my Solaris x86 with the write cach

[jira] Updated: (DERBY-1664) Derby startup time is too slow

2006-08-10 Thread David Van Couvering (JIRA)
[ http://issues.apache.org/jira/browse/DERBY-1664?page=all ] David Van Couvering updated DERBY-1664: --- Issue Type: Improvement (was: Bug) > Derby startup time is too slow > -- > > Key: DERBY-1664 >

[jira] Updated: (DERBY-1664) Derby startup time is too slow

2006-08-10 Thread David Van Couvering (JIRA)
[ http://issues.apache.org/jira/browse/DERBY-1664?page=all ] David Van Couvering updated DERBY-1664: --- Component/s: Store > Derby startup time is too slow > -- > > Key: DERBY-1664 > URL: ht