Custom Analysis - New User-mode Sampling and Tracing Analysis

Analysis name field

Enter/edit a name of this custom analysis type.

Description

Provide a short meaningful description on the analysis type you create. This information may help you easily identify the analysis type specifics later.

Collect CPU sampling data menu

Choose whether to collect information about CPU samples and related call stacks.

CPU sampling interval, ms spin box

Specify an interval between collected CPU samples in milliseconds.

Collect highly accurate CPU time check box (for Windows targets only)

Obtain more accurate CPU time data. This option causes more runtime overhead and increases result size. Administrator privileges are required.

Collect synchronization API data menu

Choose whether to collect information about synchronization wait calls and related call stacks. This analysis option helps identify where threads are waiting or enables you to compute thread concurrency. The collector instruments APIs, which causes higher overhead and increases result size.

Collect signalling API data menu

Choose whether to collect information about synchronization objects and call stacks for signaling calls. This analysis option helps identify synchronization transitions in the timeline and signalling call stacks for associated waits. The collector instruments signalling APIs, which causes higher overhead and increases result size.

Collect I/O API data menu

Choose whether to collect information about I/O calls and related call stacks. This analysis option helps identify where threads are waiting or enables you to compute thread concurrency. The collector instruments APIs, which causes higher overhead and increases result size.

Analyze user tasks, events, and counters check box

Analyze tasks, events, and counters specified in your code via the ITT API. This option causes a higher overhead and increases the result size.

Analyze user synchronization check box

Enable User synchronization API profiling to analyze thread synchronization. This option causes higher overhead and increases result size.

Stack unwinding mode menu

Choose whether collection requires online (during collection) or offline (after collection) stack unwinding. Offline mode reduces analysis overhead and is typically recommended.

Stitch stacks check box

For applications using Intel Threading Building Blocks (Intel TBB) or OpenMP* with Intel runtime libraries, restructure the call flow to attach stacks to a point introducing a parallel workload.

Analyze GPU Usage check box (for Linux* targets available with Intel HD Graphics and Intel Iris™ Graphics only)

Analyze GPU usage and identify whether your application is GPU or CPU bound.

Analyze Processor Graphics events drop-down menu

Analyze performance data from Intel HD Graphics and Intel Iris Graphics (further: Intel Graphics) based on the predefined groups of GPU metrics.

GPU sampling interval, us field

Specify an interval between GPU samples.

Trace OpenCL and Intel Media SDK Processor Graphics (Intel Graphics Driver only) check box

Capture the execution time of OpenCL™ kernels and Intel Media SDK programs on a GPU, identify performance-critical GPU tasks, and analyze the performance per GPU hardware metrics.

Disable alternative stacks for signal handlers check box (available for Linux targets)

Disable using alternative stacks for signal handlers. Consider this option for profiling standard Python 3 code on Linux.

Analyze loops check box

Extend loops analysis to collect advanced loops information, such as instructions set usage and display analysis results by loops and functions.

Managed runtime type to analyze menu

Choose a type of the managed runtime to analyze. Available options are:

• for Windows targets: combined Java* and .NET* analysis; combined Java, .NET and Python* analysis; Python only analysis

• for Linux targets: Java only analysis; combined Java and Python analysis; Python only analysis

Analyze OpenMP regions check box

Instrument the OpenMP* regions in your application to group performance data by regions/work-sharing constructs and detect inefficiencies such as imbalance, lock contention, or overhead on performing scheduling, reduction, and atomic operations. Using this option may cause higher overhead and increase the result size.

Command line name field

Enter/edit a name of the custom analysis type that will be used as an identifier when analyzing the project from the command line. Keep it short for your convenience.

Analysis identifier field

Specify a shorthand identifier to be appended to the name of each result produced by this analysis type. For example, adding the cc identifier for the Concurrency analysis result produces the following result name: r000cc, where 000 is the result number.

VTune Amplifier for Systems options only:

Select events for analysis field

Use the Events Library to select Linux Ftrace* and Android* framework events to monitor with the collector. When you select an event in the library, the VTune Amplifier provides a short event description in the information field below.

The collected data show up as tasks in the Timeline pane. You can also apply the task grouping level to view performance statistics in the grid.