[
https://issues.apache.org/jira/browse/SLING-2521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Antonio Sanso updated SLING-2521:
---------------------------------
Attachment: disabling-alias-performance.png
I re-run the test as in [0] but with the latest code (namely with SLING-2255 et
al).
It doesn't show any performance gain for this particular matter compared to [0]
# ResolveWithManyAliasTest min 10% 50% 90% max
jcr.resource-2.0.11 58 62 124 283 877
with-alias-disabled 0 0 0
0 16
(see also attache graph).
Now, while the disabling might no be the right/final solution this tests shows
that there is room for optimization (at least)
> Allow disabling sling:alias support per configuration
> -----------------------------------------------------
>
> Key: SLING-2521
> URL: https://issues.apache.org/jira/browse/SLING-2521
> Project: Sling
> Issue Type: New Feature
> Components: JCR
> Affects Versions: JCR Resource 2.1.0
> Reporter: Felix Meschberger
> Attachments: disabling-alias-performance.png
>
>
> The the JCR based ResourceResolver.resolve method currently support
> sling:alias properties on nodes to allow for resolution of translated URLs.
> This is potentially a very expensive operation particularly in the case of
> non existing resource.
> It should be analyzed whether (a) disabling sling:alias support has a
> measurable benefit on resource resolution (particularly when not finding a
> resource) and (b) whether it would be easy and simple to disable such support
> per configuration.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
