[
https://issues.apache.org/jira/browse/SLING-6180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Klimetschek updated SLING-6180:
-----------------------------------------
Attachment: SLING-6180.patch
Attaching a new version that fixes a memory leak - using the unique RequestData
instead of ServletRequest (which is often wrapped and there are multiple
instances of it per actual request) to track the requests.
> Show slowest filters sorted by time per request in filter status webconsole
> ---------------------------------------------------------------------------
>
> Key: SLING-6180
> URL: https://issues.apache.org/jira/browse/SLING-6180
> Project: Sling
> Issue Type: Improvement
> Components: Servlets
> Reporter: Alexander Klimetschek
> Attachments: SLING-6180.patch
>
>
> Current output of /system/console/status-slingfilter includes time
> measurements, including time per call. However, to analyze performance of
> component & include filters a time per request would be helpful, as these are
> called multiple times per request.
> Also, with a longer list of filters it would be nice to have this information
> sorted by their time per request, so that the "worst" offenders show up at
> the top.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
