You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Sonal Gupta (Jira)" <ji...@apache.org> on 2020/02/18 10:04:00 UTC
[jira] [Updated] (SLING-9077) Improve runtime complexity of
o.a.s.api.resource.path.PathSet's factory methods
[ https://issues.apache.org/jira/browse/SLING-9077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sonal Gupta updated SLING-9077:
-------------------------------
Attachment: PerformanceScript.sh
> Improve runtime complexity of o.a.s.api.resource.path.PathSet's factory methods
> -------------------------------------------------------------------------------
>
> Key: SLING-9077
> URL: https://issues.apache.org/jira/browse/SLING-9077
> Project: Sling
> Issue Type: Improvement
> Reporter: Dirk Rudolph
> Priority: Major
> Attachments: PerformanceScript.sh
>
>
> With SLING-8946 the PathSet used to keep track of the excluded paths for resource observation event propagation of individual ResourceProviders started to grow. (The excludes PathSet of the root-ResourceProvider / now contains all other ResourceProviders in a system).
> While registering a new ResourceProvider the context update builds a new PathSet which is optimised with in PathSet#optimize() with O(n^2). Esp. when starting up the environment this is consuming massive CPU time as it grows to O(n^3): for each RP calculate the exclusion PathSet with O(n^2).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)