[
https://issues.apache.org/jira/browse/JCR-3137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13143484#comment-13143484
]
Jukka Zitting commented on JCR-3137:
------------------------------------
Here's some rough measurements over recent releases (time between "Starting
repository" and "Repository started" messages from RepositoryImpl, plus the
total repository size after the default install):
1.6.5: install 19s, restart 2s, size 4.0MB
2.0.5: install 20s, restart 3s, size 4.2MB
2.1.6: install 21s, restart 4s, size 4.2MB
2.2.9: install 29s, restart 3s, size 6.2MB
2.3.2: install 29s, restart 4s, size 6.3MB
Not sure what's taking up so much time in the initial install, perhaps it's the
time taken by Derby to create the initial databases. Perhaps H2 would be faster?
> Slow repository startup
> -----------------------
>
> Key: JCR-3137
> URL: https://issues.apache.org/jira/browse/JCR-3137
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: jackrabbit-core
> Affects Versions: 2.3.2
> Reporter: Jukka Zitting
>
> On my reasonably fast computer I'm seeing over 30 seconds to start up a new
> repository from scratch. The startup is much faster if the repository already
> exists, so this has something to do with the initial setup. Ideally a new
> empty repository should come up in no more than a few seconds.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
