[
https://issues.apache.org/jira/browse/SLING-2521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13414876#comment-13414876
]
Carsten Ziegeler commented on SLING-2521:
-----------------------------------------
With SLING-2255 the performance win is less than outlined in [0], still
disabling seems to improve the performance under heavy load.
However, I really would like to have new numbers based on latest code (and
jackrabbit version)
I'm not in favour of a general switch, while this is the easiest to implement
it is the most dangerous for users and as soon as you have a single alias, the
whole improvement is pointless.
> 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
>
> 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
