CPU duration exceeds overall duration

Owned by Copy Space for Confluence
May 20, 2015
1 min read

Problem

The invocation sequence shows that the CPU duration exceeds the overall duration, which seems strange.

Description

The CPU time per thread is currently read using the JDK5 internal management beans (ThreadMXBean). Here we use the getCurrentThreadCpuTime method. Multiple pages suggest that the current best resolution is always dependent on the system. On most windows machines these seem to be about 15ms. (http://forums.sun.com/thread.jspa?threadID=754979)

With the current implementation on Windows platforms the CPU times might thus be higher than the shown duration. We will try to fix that in further releases but at the moment this is expected behavior.

I would say that the CPU time is still helpful to see why a method took long (does it spent the time on the CPU or is it waiting). Usually this is most important for methods that run longer than a few milliseconds. This is tracked as INSPECTIT-134

Solution

Currently there is no solution planned