[
https://issues.apache.org/jira/browse/DERBY-1664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12766531#action_12766531
]
martin commented on DERBY-1664:
-------------------------------
Startup is slow especially when database was not shut down properly. This seems
be user's problem, as it is his responsibility to ensure proper shutdown
procedure. Here is a little problem:
while embedded engine starts silently at user's request, user should shutdown
engine explicitly.
While first part conforms zero administration claim, the second part is in
direct contradiction of the claim.
Typical scenario is: application uses a connection pool - it may connect to a
production database or local testing database. For testing database, embedded
derby is used. Connection pool can start the embedded driver, but has no method
for shutdown. When application starts next times with embedded database, starts
are getting slower and slower as database grows.
I think shutdown hooks installed at engine startup should solve the situation.
This was proposed long time ago, but never implemented.
> 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.
