You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sling.apache.org by "Robert Munteanu (JIRA)" <ji...@apache.org> on 2015/10/12 11:45:06 UTC

[jira] [Closed] (SLING-4999) Check synchronization in RequestProcessorMBeanImpl

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

Robert Munteanu closed SLING-4999.
----------------------------------

> Check synchronization in RequestProcessorMBeanImpl
> --------------------------------------------------
>
>                 Key: SLING-4999
>                 URL: https://issues.apache.org/jira/browse/SLING-4999
>             Project: Sling
>          Issue Type: Improvement
>          Components: Engine
>    Affects Versions: Engine 2.4.2
>            Reporter: Carsten Ziegeler
>            Assignee: Robert Munteanu
>             Fix For: Engine 2.4.4
>
>         Attachments: 0001-SLING-4999-Check-synchronization-in-RequestProcessor.patch
>
>
> Each and every request goes through RequestProcessorMBeanImpl#addRequestData which is a synchronized block. I think this is a rather heavy bottleneck for request processing.
> In addition, some of the methods which do additional calculation are sync'ed (like getStandardDeviationDurationMsec) but others are not (like getStandardDeviationPeakRecursionDepth). This seems a little bit arbitrary to me



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)