FITS YOUR ENVIRONMENT & WORKFLOW

Intel® VTune™ Amplifier is designed to support your workflow. It works with popular compilers and languages, integrates with Microsoft Visual Studio*, and can analyze remote systems.

interface for remote system analysis
Figure 1

Profile Remote Systems
 

In many cases, you need to tune a remote server or embedded system. One option is to connect to the remote device and run the collection directly from the user interface. Or if you prefer, collect the remote data using the command line and import the results into your local user interface.

For the best performance, avoid the slow graphics of Virtual Network Computing (VNC)*. Instead, import data from the remote target, and then run the interface locally on Windows*, Linux*, or macOS*.

The user interface lets you select a local or remote target (see Fig. 1).

Note for Linux: If collectors are not installed on the remote system, Intel VTune Amplifier can install them for you. A license is not required to collect data, only to analyze it.

Collect & Analyze Data Using the Command Line
 

In addition to the user interface, you can also collect and analyze data using a command line interface (see Fig. 2). This allows lightweight collection on the target system and automation of regression analysis. Learn the command language by setting up the analysis in the Intel VTune Amplifier interface, then selecting a button to generate the command line.

interface for a command-line analysis


Figure 2

 

find hotspots in an integration with Microsoft Visual Studio
Figure 3

Tap into Microsoft Visual Studio* Integration
 

Create and debug code, and tune your application within a single environment. Start an analysis from the toolbar, see the results in Visual Studio, manage results in the solution explorer, and open a source editor from Intel VTune Amplifier’s source view.

Intel VTune Amplifier is integrated with Microsoft Visual Studio (see Fig. 3).

Use Any Compiler
 

As long as it follows industry standards, you can choose from Microsoft* compilers, the GNU Compiler Collection (GCC)*, Intel® compilers, and more. We recommend that you profile a release build (an optimized build) since the performance hotspots can be different for a debug build. Be sure to include symbols so that Intel VTune Amplifier can use your familiar function names and map results to your source code.

Use your existing compiler. No special builds are required: Just use a normal, optimized release build with symbols (see Fig. 4).

list of optimized compilers
Figure 4