You are viewing a plain text version of this content. The canonical link for it is here.

Posted to oak-issues@jackrabbit.apache.org by "Vikas Saurabh (JIRA)" <ji...@apache.org> on 2016/07/06 13:14:10 UTC

[jira] [Created] (OAK-4542) PerfLogger should also allow a threshold to log at INFO

Vikas Saurabh created OAK-4542:
----------------------------------

             Summary: PerfLogger should also allow a threshold to log at INFO
                 Key: OAK-4542
                 URL: https://issues.apache.org/jira/browse/OAK-4542
             Project: Jackrabbit Oak
          Issue Type: Improvement
            Reporter: Vikas Saurabh
            Assignee: Vikas Saurabh
            Priority: Minor


Currently, {{PerfLogger}} logs at DEBUG if time spent in operation is more that threshold ms.

We should also be able to have a second level threshold of time, beyond which the log should happen at INFO. It helps to catch cases for which the timing gets too poor at the onset of some performance issue and by the time of investigation (opportunity to add DEBUG logger) is too late already.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)