You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Felix Meschberger (JIRA)" <ji...@apache.org> on 2012/06/22 08:34:42 UTC

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

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

Felix Meschberger commented on SLING-2516:
------------------------------------------

Committed a first shot of such a tool in Rev. 1352777

The maven project is both a bundle and a standalone Java Application. When deployed as a bundle in Sling's OSGi framework it registers as a Sling request level filter and dumps information for requests to a file:

   * one line with request start time stamp, processing time in ms, request URL, method, response content type and status
   * The complete RequestProgressTracker data

When used as a standalone java application (à la java -jar ...) it takes the name of a file produced by said filter and opens a window with the list of requests collected in the file. This list can be sorted by any of the columns -- for performance analysis sorting by the request processing time is very helpful. When clicking on a request another window is opened showing the RequestProgressTracker data in three columns: time offset since start of request, time delta since last entry, entry message. These helps nicely find hotspots in request processing.
                
> Reuqest 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