Group and Filter Data
Filter by Objects
- Context menu options: Select objects of interest in the grid, right-click and choose theFilter In by Selectioncontext menu option to exclude all objects from the view other than the objects you selected. And conversely, choosing theFilter Out by Selectionhides the selected data. The filter bar at the bottom is updated to show the percentage of the displayed data by a certain metric.For example, you want to filter in the grid by the most time-consuming functionsphere_intersect:When the filter is applied, the filter bar shows that you see only 24.9% of the collected CPU Time data.
- Filter toolbar options: Select a program unit in the filtering drop-down menu (process, module, thread) to filter out your grid and Timeline view for displaying the data for this particular program unit. For example, if you select theanalyze_locksprocess introducing 51.5% of the CPU Time, the result data will display statistics for this module only and the filter bar provides an indicator that only 51354% of the CPU Time data is currently displayed:
Filter by Time Regions
Groups targeted for analysis
Identify function hotspots and distinguish problem call stacks.
For most viewpoints, Function level is the default. If application modules have debug information, you can rely on functions shown as hotspots. When debug information is incomplete or missing, you may see a number of
<unknown>functions, or samples collected on internal functions of a module might be attributed to adjacent exported functions.
Source Function/Function/Call Stackfor analyzing all instances of the inline and JITed functions
Analyze hotspots in multi-threaded applications from the function, OS (Threads) or HW (Packages, Core, Threads) perspectives.
Function/Thread/Logical Core/Call Stackfor detecting anomalies of the function execution on different threads
Function/Package/Logical Core/Thread/Call Stackfor identifying Interconnect/NUMA issues on multi-processor systems
Physical Core/Logical Core/Function/Call Stackfor identifying specific hyper-threading issues
Physical Core/Thread/Function/Call Stackand
Thread/Physical Core/Functionfor identifying issues caused by thread migration between cores
Identify slow and fast frames.
Frame Domain/Frame Duration Type/Function/Call Stack
Frame Domain/Frame Duration Type/Frame/Function/Call Stack
Identify hotspots called from OpenMP regions.
OpenMP Region/OpenMP Barrier-to-Barrier Segment/Function/Call Stackfor identifying load imbalance between different segments
OpenMP Region/OpenMP Region Duration Type/Function/Call Stackfor analyzing fast/slow OpenMP region instances
Analyze the CPU activity while the GPU was either idle or executing some code
Render and GPGPU Packet Stage / Function / Call Stack
Render and GPGPU Packet Stage / Thread / Function / Call Stack