Uploaded image for project: 'Sling'
  1. Sling
  2. SLING-9535

Improve performance of sling:alias Query when Optimize alias resolution is activated

    XMLWordPrintableJSON

    Details

      Description

      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:

      (query=SELECT sling:alias FROM nt:base WHERE sling:alias IS NOT NULL, path=*, property=[sling:alias=[is not null]])

      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.

       

      Thanks

       

        Attachments

        1. image-2020-06-19-18-29-24-335.png
          18 kB
          Leonardo Derks
        2. image-2020-06-19-18-33-21-657.png
          8 kB
          Leonardo Derks

          Issue Links

            Activity

              People

              • Assignee:
                rombert Robert Munteanu
                Reporter:
                Leonardo Derks Leonardo Derks
              • Votes:
                2 Vote for this issue
                Watchers:
                6 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 19.5h
                  19.5h