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

Posted to dev@sling.apache.org by "Justin Edelson (JIRA)" <ji...@apache.org> on 2012/06/27 13:53:44 UTC

[jira] [Commented] (SLING-2516) Request Performance Analysis helper

    [ https://issues.apache.org/jira/browse/SLING-2516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13402160#comment-13402160 ] 

Justin Edelson commented on SLING-2516:
---------------------------------------

FYI - the RequestProgresssTracker data can already be dumped to a file by setting the log level on org.apache.sling.engine.impl.debug.RequestProgressTrackerLogFilter to DEBUG.
                
> Request Performance Analysis helper
> -----------------------------------
>
>                 Key: SLING-2516
>                 URL: https://issues.apache.org/jira/browse/SLING-2516
>             Project: Sling
>          Issue Type: New Feature
>          Components: Extensions
>            Reporter: Felix Meschberger
>            Assignee: Felix Meschberger
>
> To measure overall request performance, Sling has a RequestProgressTracker where each request is tracking progress as  a request is processed. Normally this RequestProgressTracker is just collected but other than being presented in the "Recent Requests" page of the web console not further used.
> To track down generic bottle necks and processing peaks while doing load tests on a Sling system, it would be usefull if the RequestProgressTracker data could be dumped into a file which can later be displayed and analysed.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira