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

High resource consumption when activating/deactivating ResourceProviders

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Blocker
    • Resolution: Duplicate
    • None
    • None
    • ResourceResolver
    • None

    Description

      With SLING-8946 the updating of all ResourceProviders when their exclude path set changes was introduced to prevent non-deterministic behaviour of resource observation.

      This change though caused calling updateProviderContext() and ResourceProviderHandler#update() on every registered ResourceProviderHandler when a new ResourceProvider was activated/deactivated no matter if the paths actually intersect.

      This is quite resource consuming (processing time and memory) and should be reduced to update only those handlers that actually intersect with the handler added/removed.

      Attachments

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            Unassigned Unassigned
            diru Dirk Rudolph
            Votes:
            0 Vote for this issue
            Watchers:
            4 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 - 40m
                40m

                Slack

                  Issue deployment