[
https://issues.apache.org/jira/browse/SLING-3290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13874746#comment-13874746
]
Antonio Sanso commented on SLING-3290:
--------------------------------------
[~justinedelson] adding profile information
{code}
org.apache.sling.performance.tests.StartupWithManyVanityPath.runTest()","18272"
"org.apache.sling.performance.PerformanceTest$Helper.init(String, Session,
SlingRepository)","18272"
"org.apache.sling.resourceresolver.impl.mapping.MapEntries.<init>(MapConfigurationProvider,
BundleContext, EventAdmin)","18272"
"org.apache.sling.resourceresolver.impl.mapping.MapEntries.doInit()","18272"
"org.apache.sling.resourceresolver.impl.mapping.MapEntries.loadVanityPaths(ResourceResolver,
Map)","18252"
"org.apache.sling.resourceresolver.impl.helper.ResourceIteratorDecorator.next()","15500"
{code}
as expected the looping through the search results is the "bottleneck"
> Long startup time with many vanityPath or alias
> -----------------------------------------------
>
> Key: SLING-3290
> URL: https://issues.apache.org/jira/browse/SLING-3290
> Project: Sling
> Issue Type: Improvement
> Reporter: Antonio Sanso
> Assignee: Antonio Sanso
> Labels: vanity
> Attachments: 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.1.5#6160)
