[SLING-9077] Improve runtime complexity of o.a.s.api.resource.path.PathSet's factory methods

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Won't Fix
• Assignee: Unassigned
• Reporter: Dirk Rudolph
• Created: 17/Feb/20 12:34
• Updated: 09/Jun/20 16:13
• Resolved: 08/Jun/20 11:33

Description

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).

Issue Links

• relates to: SLING-8946 Non-deterministic shadowing of resource observation
• relates to: SLING-9365 Optionally don't create resource providers for servlets
• links to: GitHub Pull Request #18