[ 
https://issues.apache.org/jira/browse/SLING-9040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17095131#comment-17095131
 ] 

Dirk Rudolph commented on SLING-9040:
-------------------------------------

And there is SLING-9077 open, which reduces the time complexity of the problem 
noticeably. Not sure though if the introduced complexity in the PathSet is 
worth it, considering SLING-9365 will be a more elegant approach if feasible.

 

> High resource consumption when activating/deactivating ResourceProviders
> ------------------------------------------------------------------------
>
>                 Key: SLING-9040
>                 URL: https://issues.apache.org/jira/browse/SLING-9040
>             Project: Sling
>          Issue Type: Bug
>          Components: ResourceResolver
>            Reporter: Dirk Rudolph
>            Assignee: Robert Munteanu
>            Priority: Blocker
>             Fix For: Resource Resolver 1.6.18
>
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> 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.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to