[
https://issues.apache.org/jira/browse/SLING-12879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18113303#comment-18113303
]
Georg Henzler commented on SLING-12879:
---------------------------------------
My understanding is that we should aim for the optimised alias resolution (
[ResourceResolverFactoryActivator.java#L312|https://github.com/apache/sling-org-apache-sling-resourceresolver/blob/8fbccca65c243e8fd15bc2089ee41d081a3afa0e/src/main/java/org/apache/sling/resourceresolver/impl/ResourceResolverFactoryActivator.java#L312]
SLING-12025)
We cannot change the fact that we need the 480k aliases (we have 2 Mio pages,
it's a large instance).
With the proposed index installed we are now down to a startup time of 32 min -
while this is better than 2h it's still not workable: we need to get down to
~1min, otherwise it's problematic for our operating procedures.
[~reschke] Do you see a way to initialise the cache with the 480k aliases
within a minute?
> ResourceResolver: add option to run alias initializer in background
> -------------------------------------------------------------------
>
> Key: SLING-12879
> URL: https://issues.apache.org/jira/browse/SLING-12879
> Project: Sling
> Issue Type: Sub-task
> Components: ResourceResolver
> Reporter: Julian Reschke
> Assignee: Julian Reschke
> Priority: Major
> Fix For: Resource Resolver 1.12.12, Resource Resolver 2.0.2
>
> Attachments: image-2026-09-08-13-34-48-536.png,
> image-2026-09-08-13-55-36-085.png, log-analyse-aem-vostra.json,
> resourceresolver-index-1.0.zip, slingResourceResolver-3.10.json
>
>
> This will add that option, but keep it disabled.
> For now it will only be tested in unit tests.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
