[jira] [Resolved] (SLING-4568) Performance: MergingResourceProvider.ParentHidingHandler adds about 30pp rendering overhead

["Carsten Ziegeler (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SLING-4568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carsten Ziegeler resolved SLING-4568.
-------------------------------------
    Resolution: Fixed

Thanks for your work and patch, Joel. I've applied the parent hiding handler part of your patch.
A configuration that defers from the search path is causing for trouble. It will get out of sync. And we also might want to have a more dynamic search path in the future (e.g. for per tenant).

> Performance: MergingResourceProvider.ParentHidingHandler adds about 30pp 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
>            Assignee: Carsten Ziegeler
>              Labels: performance
>             Fix For: Resource Merger 1.2.10
>
>         Attachments: SLING-4568_exclude_search_paths.patch, SLING-4568_experimental_cache.patch
>
>
> When I was analysing all read properties, I 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-35pp faster just by commenting out the constructor code.
> Apache Benchmark results with normal ParentHidingHandler:
> {quote}
>   50%    272
>   66%    276
>   75%    278
>   80%    281
>   90%    289
>   95%    301
>   98%    493
>   99%    497
> {quote}
> Results with commented out ParentHidingHandler constructor: 
> {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)