[
https://issues.apache.org/jira/browse/SLING-12879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18112520#comment-18112520
]
Jan Stettler edited comment on SLING-12879 at 9/8/26 1:57 PM:
--------------------------------------------------------------
Hi,
I have a question regarding this ticket.
We upgraded to {*}AEM 6.5 LTS SP2{*}, and since the update our instances have
become extremely slow for at least {*}two hours after startup{*}.
The issue appears to be related to
{*}org.apache.sling.resourceresolver-1.12.12.jar{*}.
We have *208 Live Copies* with {*}3 languages{*}. Two of these languages use
{*}{{sling:alias}}{*}, and each language contains approximately {*}1,000
pages{*}.
With this setup, we end up with more than {*}480,000 aliases{*}. As a result:
* Instance startup takes roughly *2 hours* before the system becomes
operational.
* The background alias cache population also takes about *2 hours* before the
instance reaches acceptable performance.
Script INFO -> aliasCount = [414505]
Script INFO -> aliasCountUnique = [3675]
During the cache build process, page rendering times increase to {*}5 to 7
seconds per request{*}, as the system has to process a very large number of
resources.
Before upgrading to SP2, when using
{*}org.apache.sling.resourceresolver-1.12.08.jar{*}, page rendering typically
took only {*}0.7 to 1.5 seconds{*}.
Prior to SP2, we had alias caching disabled, and the system performed well.
Is there a way to restore the previous behaviour?
Specifically, would it be possible to fall back to the non-cached alias
resolution mechanism until the cache has been fully built, since this appears
to be significantly faster in our environment?
Thanks in advance for your help.
was (Author: JIRAUSER314579):
Hi,
I have a question regarding this ticket.
We upgraded to {*}AEM 6.5 LTS SP2{*}, and since the update our instances have
become extremely slow for at least {*}two hours after startup{*}.
The issue appears to be related to
{*}org.apache.sling.resourceresolver-1.12.12.jar{*}.
We have *208 Live Copies* with {*}3 languages{*}. Two of these languages use
{*}{{sling:alias}}{*}, and each language contains approximately {*}1,000
pages{*}.
With this setup, we end up with more than {*}480,000 aliases{*}. As a result:
* Instance startup takes roughly *2 hours* before the system becomes
operational.
* The background alias cache population also takes about *2 hours* before the
instance reaches acceptable performance.
During the cache build process, page rendering times increase to {*}5 to 7
seconds per request{*}, as the system has to process a very large number of
resources.
Before upgrading to SP2, when using
{*}org.apache.sling.resourceresolver-1.12.08.jar{*}, page rendering typically
took only {*}0.7 to 1.5 seconds{*}.
Prior to SP2, we had alias caching disabled, and the system performed well.
Is there a way to restore the previous behaviour?
Specifically, would it be possible to fall back to the non-cached alias
resolution mechanism until the cache has been fully built, since this appears
to be significantly faster in our environment?
Thanks in advance for your help.
> 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
>
>
> 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)
