[SLING-3848] JcrNodeResource takes too long and initializes too much too soon

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: JCR Resource 2.3.8, API 2.8.0
• Component/s: JCR
• Assignee: Carsten Ziegeler
• Reporter: Rob Ryan
• Created: 13/Aug/14 21:46
• Updated: 31/Aug/14 08:58
• Resolved: 25/Aug/14 06:32

Description

In a performance test expected to reflect reasonably real-world conditions (50 concurrent users of a mixed load 'forum' type application) I found org.apache.sling.jcr.resource.internal.helper.jcr.JcrNodeResource.JcrNodeResource(ResourceResolver, Node, ClassLoader) taking more than 20% of time used. The majority of this time was spent in setting the resource metadata and to a lesser extent the resource type.

Because the metadata especially is not often accessed and even the resource type is not always accessed, delaying these initializations led to a noticeable performance improvement.

The attached patch delays resourcetype lookup and metadata lookups until needed.