Problem: CPU time for Hotspots or Threading Analysis is Too Low
- The analysis run was very short and the target consumed little CPU time.
- CPU time may be inaccurate for targets that work in short quanta less than the scheduler tick interval. For example, this can happen for frame-by-frame computation in video decoders. To capture CPU time more accurately on Windows* OS, you need to run the analysis with the accurate CPU time detection mode enabled.
- Extend the duration of the analysis run.
- Windows OS only: Enable accurate CPU time detection. To do this for the Hotspots or Threading analysis, it is enough to run theVTunewith administrative permissions. You may also enable this option explicitly in the custom analysis configuration by checking theProfilerCollect highly accurate CPU timebox. Make sure to extend maximum size of raw collector data.