You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Julian Reschke (Jira)" <ji...@apache.org> on 2026/09/02 11:49:00 UTC
[jira] [Resolved] (SLING-13275) Backport to 1.x - cache results of ResourceResolver.getResourceParentType
[ https://issues.apache.org/jira/browse/SLING-13275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Julian Reschke resolved SLING-13275.
------------------------------------
Resolution: Done
> Backport to 1.x - cache results of ResourceResolver.getResourceParentType
> -------------------------------------------------------------------------
>
> Key: SLING-13275
> URL: https://issues.apache.org/jira/browse/SLING-13275
> Project: Sling
> Issue Type: Task
> Components: ResourceResolver
> Reporter: Roy Teeuwen
> Priority: Major
> Fix For: Resource Resolver 1.12.16
>
>
> Backport of SLING-12244 to the 1.x maintenance branch.
> The change was applied to master (commit 3abb019aa7c242ebbac5bac756f07845f774b080) and released in Resource Resolver 2.0.0, but was never backported, so the 1.x line still lacks it.
> h3. Original description (SLING-12244)
> {quote}
> In the context of Sling Models I found that a lot of calls to ResourceResolver.getParentResourceType(Resource) are done, which result in repository access. But this can happen also outside of it.
> In a simple example (AEM wknd page) I found in total 320 calls to in total 36 resources. Caching these can save around 280 requests to the repository, which a reduction in repository access in the range of 2-3% when rendering the complete page.
> {quote}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)