[
https://issues.apache.org/jira/browse/SLING-11618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joerg Hoh updated SLING-11618:
------------------------------
Description:
With the changes in SLING-10582 the filter timing was changed to be recorded in
microseconds as well, while the Webconsole Plugin still expects miliseconds.
This should be fixed, the unit should still be microseconds.
was:
With the changes in SLING-10582 the filter timing was changed to be recorded in
microseconds as well.
Previously the filter status was assuming a milisecond granularity and
calculated the average duration per invocation in microseconds.
Now the durations are in microseconds instead, so the timing itself should be
adjusted. But no need to have a nanosecond resolution.
Summary: Webconsole: FilterStatus prints timings with wrong unit
(was: Webconsole: FilterStatus prints timings in µs instead of nanosecs)
> Webconsole: FilterStatus prints timings with wrong unit
> --------------------------------------------------------
>
> Key: SLING-11618
> URL: https://issues.apache.org/jira/browse/SLING-11618
> Project: Sling
> Issue Type: Improvement
> Components: Engine
> Affects Versions: Engine 2.12.0
> Reporter: Joerg Hoh
> Assignee: Joerg Hoh
> Priority: Major
>
> With the changes in SLING-10582 the filter timing was changed to be recorded
> in microseconds as well, while the Webconsole Plugin still expects
> miliseconds.
> This should be fixed, the unit should still be microseconds.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
