Viewpoint

Hotspots

Helps identify hotspots - code regions in the application that consume a lot of CPU time.

Advanced Hotspots, Basic Hotspots, Concurrency, Locks and Waits

Hotspots by CPU Usage

Helps identify hotspots - code regions in the application that consume a lot of CPU time. CPU time is broken down into CPU usage states: idle, poor, fair, and good.

Basic Hotspots, Concurrency, Locks and Waits

Hotspots by Thread Concurrency

Helps identify hotspots - code regions in the application that consume a lot of CPU time. CPU time is broken down into thread concurrency states: idle, poor, fair, good, and over.

Concurrency, Locks and Waits

Locks and Waits

Shows how your application is utilizing available CPU cores and helps identify the cause of ineffective utilization, for example: threads waiting too long on synchronization objects (locks), I/O, or timers while CPU cores are underutilized. CPU time is represented by bars colored according to the CPU utilization level during the wait.

Concurrency, Locks and Waits

Hardware Events

Displays statistics of monitored hardware events: estimated count and/or the number of samples collected. Use this view to identify code regions (modules, functions, code lines, and so on) with the highest activity for an event of interest.

All hardware-level event-based sampling analysis types

Hardware Issues

Helps identify where the application is not making the best use of available hardware resources. This viewpoint displays metrics derived from hardware performance counters. Hover over the highlighted metrics values in the grid to read why the extreme value might represent a performance problem.

All hardware-level event-based sampling analysis types

General Exploration

Helps identify where the application is not making the best use of available hardware resources. This viewpoint displays metrics derived from hardware events. The Summary window reports the overall metrics for the entire execution along with explanations of the metrics. From the Bottom-up and Top-down Tree windows you can locate the hardware issues in your application. Cells are highlighted when potential opportunities to improve performance are detected. Hover over the highlighted metrics in the grid to see explanations of the issues.

General Exploration

Memory Usage

Helps understand how effectively your application uses memory resources and identify potential memory access related issues like excessive access to remote memory on NUMA platforms, hitting DRAM or Intel® QuickPath Interconnect (Intel QPI) bandwidth limit, and others. It provides various performance metrics for both the application code and memory objects arrays.

Memory Access and General Exploration with the Analyze memory bandwidth option enabled

Platform Power Analysis

Helps identify where the application is generating idle and wake-up behavior that can lead to inefficient use of energy. Where possible, it provides data from both the OS and hardware perspective, such as the detailed C-state residency report that shows the OS requested time in deep sleep states compared to the actual residency the hardware indicated.

Energy Analysis