Set Up Analysis Target

When you create a project for the Intel® VTune™ Amplifier performance analysis, you have to specify what you want to profile - your analysis target, which could be an executable file, a process, or a whole system.

Supported Targets

Before starting an analysis, make sure your target and system are compiled/configured properly for performance profiling.

VTune Amplifier supports analysis targets developed and runnable in the following environments:

Development Environment Integration

Target Platform

Programming Language

Programming Model

Virtual Environment

Containers

LXC*, Docker*, Mesos*

Specify Your Target

To specify your target for analysis:

  1. Click the New Project button on the toolbar to create a new project.

    If you need to re-configure the target for an existing project, click the Configure Analysis toolbar button.

    The Configure Analysis window opens. By default, the project is pre-configured to run the Hotspots analysis in the user-mode sampling mode with the Launch Application target type on the Local Host target system.

  2. If you do not run an analysis on the local host, click the Browse button from the WHERE pane and select an appropriate target system.

    The target system can be the same as the host system, which is a system where the VTune Amplifier GUI is installed. If you run an analysis on the same system where the VTune Amplifier is installed (i.e. target system=host system), such a target system is called local. Target systems other than local are called remote systems. But both local and remote systems are accessible targets, which means you can access them either directly (local) or via a connection (for example, SSH connection to a remote target).

    Local Host

    Run an analysis on the local host system.

    Note

    This type of the target system is not available for macOS*.

    Remote Linux (SSH)

    Run an analysis on a remote regular or embedded Linux* system. VTune Amplifier uses the SSH protocol to connect to your remote system. Make sure to fill in the SSH Destination field with the username, hostname, and port (if required) for your remote Linux target system as username@hostname[:port].

    Android Device (ADB)

    Run an analysis on an Android device. VTune Amplifier uses the Android Debug Bridge* (adb) to connect to your Android device. Make sure to specify an Android device targeted for analysis in the ADB Destination field. When the ADB connection is set up, the VTune Amplifier automatically detects available devices and displays them in the menu.

    Arbitrary Host (not connected)

    Create a command line configuration for a platform NOT accessible from the current host, which is called an arbitrary target.

  3. From the WHAT pane, specify an application to launch or click the Browse button to select a different target type:

    Launch Application (pre-selected)

    Enable the Launch Application pane and choose and configure an application to analyze, which can be either a binary file or a script.

    Note

    This target type is not supported for the Hotspots analysis of Android applications. Use the Attach to Process or Launch Android Package types instead.

    Attach to Process

    Enable the Attach to Process pane and choose and configure a process to analyze.

    Profile System

    Enable the Profile System pane and configure the system-wide analysis that monitors all the software executing on your system.

    Launch Android Package

    Enable the Launch Android Package pane to specify the name of the Android* package to analyze and configure target options.

Note

For driverless event-based sampling data collection, VTune Amplifier supports local and remote Launch Application, Attach to Process and Profile System target types but their support fully depends on the Linux Perf profiling credentials specified in the /proc/sys/kernel/perf_event_paranoid file and managed by the administrator of your system using root credentials. For more information see the perf_event related configuration files topic at http://man7.org/linux/man-pages/man2/perf_event_open.2.html. By default, only user processes profiling at the both user and kernel spaces is permitted, so you need granting wider profiling credentials via the perf_event_paranoid file to employ the Profile System target type.

What's Next

As soon as you specified the analysis system and target, you may either click the Start button to run the Hotspots analysis or click the Browse button on the HOW pane to choose a different analysis type.

For more complete information about compiler optimizations, see our Optimization Notice.
Select sticky button color: 
Orange (only for download buttons)