You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Joel Richard (JIRA)" <ji...@apache.org> on 2015/04/02 15:30:54 UTC
[jira] [Created] (SLING-4568) Performance:
MergingResourceProvider.ParentHidingHandler adds about 30% rendering
overhead
Joel Richard created SLING-4568:
-----------------------------------
Summary: Performance: MergingResourceProvider.ParentHidingHandler adds about 30% rendering overhead
Key: SLING-4568
URL: https://issues.apache.org/jira/browse/SLING-4568
Project: Sling
Issue Type: Bug
Components: ResourceResolver
Affects Versions: Resource Merger 1.2.8
Reporter: Joel Richard
Priority: Critical
When I was analysing all read properties, I have noticed a recurring pattern with sling:hideChildren and jcr:primaryType and that more than 40% of the read properties are sling:hideChildren. I figured out that sling:hideChildren is read for all parents in MergingResourceProvider.ParentHidingHandler and that the requests are processed 30-35% faster just by uncommenting the constructor code.
Apache Benchmark results with ParentHidingHandler:
{quote}
50% 272
66% 276
75% 278
80% 281
90% 289
95% 301
98% 493
99% 497
{quote}
With uncommented ParentHidingHandler:
{quote}
50% 185
66% 188
75% 191
80% 194
90% 202
95% 210
98% 333
99% 338
{quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)