Improve performance of sling:alias Query when Optimize alias resolution is activated in the Resource Resolver Factory:
By checking the logs at startup this query is executed:
The part that will be good to improve is that the query is not executed for path=, instead a predefined set of locations is used.*
(Something similar as it is for the Vanity Paths will be nice):
Then if none fo these are configured then the query is executed with path=*.
In our project several versions are created per page and it turns out that the sling:alias found under /jcr:system/jcr:versionStorage are also including in the query exceeding the 10000 limit mentioned in the warning message of the property:
This might have an impact on the startup time and on the alias update time if the number of aliases is huge (over 10000)
We might have a different approach to solve our issue but did not want to leave this topic in the air. Might be also a good improvement for others.