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 2021/07/05 19:35:00 UTC

[jira] [Resolved] (SLING-10582) Filter timing should have microsecond resolution

     [ https://issues.apache.org/jira/browse/SLING-10582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Joerg Hoh resolved SLING-10582.
-------------------------------
    Resolution: Fixed

> Filter timing should have microsecond resolution
> ------------------------------------------------
>
>                 Key: SLING-10582
>                 URL: https://issues.apache.org/jira/browse/SLING-10582
>             Project: Sling
>          Issue Type: Improvement
>          Components: Engine
>    Affects Versions: Engine 2.7.6, Engine 2.7.8
>            Reporter: Joerg Hoh
>            Assignee: Joerg Hoh
>            Priority: Major
>             Fix For: Engine 2.7.10
>
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> Since SLING-5275 the RequestProgressTracker logs with a granularity of microseconds but the filter timing entries themselves are still on a Milisecond granularity. They should be changed to use microseoncds as well.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)