You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Joerg Hoh (Jira)" <ji...@apache.org> on 2022/11/06 11:47:00 UTC
[jira] [Commented] (SLING-11618) Webconsole: FilterStatus prints timings with wrong unit
[ https://issues.apache.org/jira/browse/SLING-11618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17629457#comment-17629457 ]
Joerg Hoh commented on SLING-11618:
-----------------------------------
[~cziegeler] You are right, getTime() still returns miliseconds.
{noformat}
public long getTimePerCall() {
return (getCalls() > 0) ? (time.get() / getCalls()) : -1;
}
{noformat}
is much much cleaner and is also much more accurate.
> 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
> Fix For: Engine 2.13.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> 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)