[
https://issues.apache.org/jira/browse/SLING-12244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joerg Hoh updated SLING-12244:
------------------------------
Description:
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 the range of 2-3% when it comes to repository access when
rendering the complete page.
was:
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, which can around 280 requests to the repository, which a reduction
in the range of 2-3% when it comes to repository access when rendering the
complete page.
> cache results of ResourceResolver.getResourceParentType
> -------------------------------------------------------
>
> Key: SLING-12244
> URL: https://issues.apache.org/jira/browse/SLING-12244
> Project: Sling
> Issue Type: Task
> Components: ResourceResolver
> Reporter: Joerg Hoh
> Assignee: Joerg Hoh
> Priority: Major
>
> 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 the range of 2-3% when it comes to repository access
> when rendering the complete page.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
