[SLING-9040] High resource consumption when activating/deactivating ResourceProviders

• Type: Bug
• Status: Resolved
• Priority: Blocker
• Resolution: Duplicate
• Component/s: ResourceResolver
• Assignee: Unassigned
• Reporter: Dirk Rudolph
• Created: 30/Jan/20 14:37
• Updated: 21/Aug/20 12:08
• Resolved: 21/Aug/20 12:08

Description

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.

Issue Links

• duplicates: SLING-8946 Non-deterministic shadowing of resource observation
• is caused by: SLING-8946 Non-deterministic shadowing of resource observation
• links to: GitHub Pull Request #17