[OAK-3361] Reduce PerfLogger isDebugEnabled overhead

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 1.3.4
• Fix Version/s: 1.0.33, 1.2.17, 1.3.6, 1.4
• Component/s: core
• Labels: performance
• Assignee: Marcel Reutegger
• Reporter: Joel Richard
• Created: 07/Sep/15 10:06
• Updated: 12/Jul/16 15:24
• Resolved: 07/Sep/15 12:24

Description

If a node is cached, 1/4 of the time which is used to call DocumentNodeStore.getNode is spent in PerfLogger.start and PerfLogger.end just for checking whether or not debug logging is enabled (this is likely much less if no TurboFilters are used).

To reduce the overhead of the PerfLogger, it should not check if debug is enabled in end() if start is below 0 anyway. Moreover, it would help to check only every second if debug is really enabled.

Issue Links

• is required by: OAK-4542 PerfLogger should also allow a threshold to log at INFO