[
https://issues.apache.org/jira/browse/DERBY-1664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12630622#action_12630622
]
Gili commented on DERBY-1664:
-----------------------------
This is still an issue even in the latest build. Given the fact that Derby is
most likely going to be used on client-side applications you should be aiming
for something along the lines of 300ms if tables already exist. Anything more
leads to a (very) noticeable delay when launching applications.
> 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: 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.
