You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Robert Munteanu (Jira)" <ji...@apache.org> on 2020/01/30 23:01:00 UTC
[jira] [Assigned] (SLING-9040) High resource consumption when
activating/deactivating ResourceProviders
[ https://issues.apache.org/jira/browse/SLING-9040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Munteanu reassigned SLING-9040:
--------------------------------------
Assignee: Robert Munteanu
> 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)