[
https://issues.apache.org/jira/browse/SLING-3290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14084569#comment-14084569
]
Antonio Sanso commented on SLING-3290:
--------------------------------------
[~fmeschbe] thanks a lot for your comment.
bq. full-work-on-update.
just to be sure. Did you "follow" the update of MapEntries done in SLING-3505.
The full-work-on-update is not there anymore :)
About the /etc/map the things that doesn't make me eager of this solution is
the full duplication of the content (namely the same information is maintained
completely in two location) and the problem to keep those on sync. E.g. what
would happen if I manually delete one vanity path entry from etc/map :S ?
> Long startup time with many vanityPath
> --------------------------------------
>
> Key: SLING-3290
> URL: https://issues.apache.org/jira/browse/SLING-3290
> Project: Sling
> Issue Type: Improvement
> Components: ResourceResolver
> Reporter: Antonio Sanso
> Assignee: Antonio Sanso
> Labels: vanity
> Attachments: SLING-3290-patch.txt, StartupWithManyVanityPath.jpg
>
>
> When many vanityPath or alias are present the system take long time to
> startup , Same when a vanityPath/alias is removed or updated .
> The reason behind is the usage of a query that updates the global mapentry.
> I have added a new Test to the performance test suite and this is the outcome
> {code}
> 0 vanityPath 16ms
> 1 vanityPath 19ms
> 10 vanityPath 70ms
> 100 vanityPath 111ms
> 1000 vanityPath 200ms
> 10000 vanityPath 1173ms
> 30000 vanityPath 3358ms
> {code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
