[
https://issues.apache.org/jira/browse/SLING-12879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18113372#comment-18113372
]
Joerg Hoh commented on SLING-12879:
-----------------------------------
[~henzlerg] querying 500k nodes in a minute is unrealistic; I see 2 options to
achieve a faster startup:
* work without the cache
* initialize the cache in the background; and while the cache is not populated,
the system resolves aliases directly (of course with an performance impact).
How was the performance of the Alias initialization before? Because the
initialization in the background plus the pagination was introduced only
recently (well, 2 years ago?), but I wonder if the previous blocking,
single-query-based alias initialization was significantly faster.
> 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)
