Intel® VTune™ Amplifier

Running Platform Analysis from the Command Line

CPU/GPU Concurrency Analysis

You can use the amplxe-cl command tool to profile applications that do computations on an Intel® HD Graphics and Intel® Iris™ Graphics device.

Analyzing GPU activity helps you identify whether:

The CPU/GPU Concurrency analysis type explores code execution on the various CPU and GPU cores in your system, correlates CPU and GPU activity and identifies whether your application is GPU or CPU bound.

To perform CPU/GPU Concurrency analysis from command line, use the collect action and specify the cpugpu-concurrency predefined analysis type:

$ amplxe-cl -collect cpugpu-concurrency -- <target> [target_options]

where:

Example

This example shows how to run CPU/GPU Concurrency analysis on myApplication:

 $ amplxe-cl -collect cpugpu-concurrency -- home/test/myApplication

GPU Hotspots Analysis

Use this analysis type to identify GPU tasks with high GPU utilization and estimate the effectiveness of this utilization. The tool infrastructure automatically aligns clocks across all cores in the entire system so that you can analyze some CPU-based workloads together with GPU-based workloads within a unified time domain.

Use the GPU Hotspots analysis to:

Use the following command line syntax to run the GPU Hotspots analysis:

$ amplxe-cl -collect gpu-hotspots [<-knob> <knob_name=knob_option>] -- <target> [target_options]

Note

For the most current information on available knobs (configuration options) for the GPU Hotspots analysis, enter:

$ amplxe-cl -help collect gpu-hotspots

Example

Run GPU Hotspots analysis with enabled OpenCL™ kernels tracing on specified application.

$ amplxe-cl -collect gpu-hotspots -knob enable-gpu-runtimes=true -- home/test/myApplication

Disk Input and Output Analysis

This analysis type uses the hardware event-based sampling collection and system-wide Ftrace* collection to provide a consistent view of the storage sub-system combined with hardware events and an easy-to-use method to match user-level source code with I/O packets executed by the hardware.

The analysis actively relies on the data produced by the kernel block driver system. In case your platform utilizes a non-standard block driver sub-system (for example, user-space storage drivers), disk metrics will not be available in the analysis type.

Use the Disk Input and Output analysis to identify:

Use the following command line syntax to run the Disk Input and Output analysis:

$ amplxe-cl -collect disk-io -- <target> [target_options]

Prerequisites:

Examples

Example 1: Disk Input and Output Analysis with a Target Application

This example shows how to run the Disk Input and Output analysis with specified target application and enabled system-wide profiling:

$ amplxe-cl -collect disk-io -analyze-system -- home/test/myApplication

Example 2: Disk Input and Output Analysis without a Target Application

This example shows how to run a system-wide Disk Input and Output analysis without specified target application for 30 seconds:

$ amplxe-cl -collect disk-io --duration 30

System Overview Analysis

Note

System Overview analysis is provided by Intel® VTune™ Amplifier for Systems only.

System Overview analysis evaluates general behavior of Linux* or Android* target systems and correlates power and performance metrics with IRQ handling. This analysis type uses the Driverless Event-Based Sampling Collection.

Use the following command line syntax to run the System Overview analysis:

$ amplxe-cl -collect system-overview [<-knob> <knob_name=knob_option>] -- <target>

Note

For the most current information on available knobs (configuration options) for the System Overview analysis, enter:

$ amplxe-cl -help collect system-overview

Example

The following example runs the System Overview analysis on a guest OS via Kernel-based Virtual Machine with specified kallsyms and modules files paths.

$ amplxe-cl -collect system-overview -analyze-kvm-guest -kvm-guest-kallsyms=/home/vtune/[guest]/kallsyms -kvm-guest-modules=/home/vtune/[guest]/modules

See Also