[SLING-2255] Improve JcrResourceResolver#resolve performance when big number of vanityPath are present

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: JCR Resource 2.0.10
• Fix Version/s: JCR Resource 2.1.0
• Component/s: JCR
• Assignee: Carsten Ziegeler
• Reporter: Antonio Sanso
• Created: 25/Oct/11 14:18
• Updated: 18/May/12 07:47
• Resolved: 16/Mar/12 08:16

Description

At the moment the performance of JcrResourceResolver#resolve is tight with the number of sling:vanityPath present in the repository.
Large number of vanityPath means large response time specially in the worse case scenario (namely huge number of vanityPath and request that doesn't match any vanityPath) but also in the average cases.
Sling currently employs generic regexps also for vanityPath, but since the regex behind a vanityPath is well know there is room for optimization.
I'll attach a graphs that shows the situation and a potential patch.