sling-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dirk Rudolph (Jira)" <j...@apache.org>
Subject [jira] [Resolved] (SLING-9077) Improve runtime complexity of o.a.s.api.resource.path.PathSet's factory methods
Date Mon, 08 Jun 2020 11:34:00 GMT

     [ https://issues.apache.org/jira/browse/SLING-9077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Dirk Rudolph resolved SLING-9077.
---------------------------------
    Resolution: Won't Fix

Closing in favour of the approach in SLING-9365. Reducing the number of ResourceProviders
keeps the PathSets used by the resource resolver logic reasonable small. Completing this improvement
would not add much value but unreasonable complexity. 

> 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
>
>          Time Spent: 50m
>  Remaining Estimate: 0h
>
> 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)

Mime
View raw message