You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Rob Ryan (JIRA)" <ji...@apache.org> on 2014/08/13 23:50:18 UTC
[jira] [Updated] (SLING-3848) JcrNodeResource takes too long and
initializes too much too soon
[ https://issues.apache.org/jira/browse/SLING-3848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rob Ryan updated SLING-3848:
----------------------------
Attachment: sling.api.diff
This patch introduces a new protected method in the ResourceMetaData class so that subclasses can introduce values into the map as they are accessed.
> JcrNodeResource takes too long and initializes too much too soon
> ----------------------------------------------------------------
>
> Key: SLING-3848
> URL: https://issues.apache.org/jira/browse/SLING-3848
> Project: Sling
> Issue Type: Improvement
> Components: JCR
> Reporter: Rob Ryan
> Attachments: sling.api.diff
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.2#6252)