User Guide

  • 2020
  • 06/18/2020
  • Public Content
Contents

VTune
Profiler
Filenames and Locations

Intel® VTune™
Profiler
generates the following file types:
The default installation path for the VTune
Profiler
varies with the product shipment:

Analysis Result Files

File Type
Default Location
Result (
*.
vtune
) produced with preset analysis type
The location of the result files is controlled by the user. The default location for
VTune
Profiler
is:
  • On Linux:
    /root/intel/
    vtune
    /projects/[project directory]/r@@@{at}
  • On Windows:
    • VTune
      Profiler
      Results\[project name]\r@@@{at}
      directory in the solution directory (Visual Studio* IDE)
    • %USERPROFILE%\My Documents\
      Profiler
      XE\Projects\[project directory]\r@@@{at}
      directory (Standalone
      VTune
      Profiler
      GUI)
Result (
*.
vtune
) produced with a custom analysis type
The location of the result files is controlled by the user. The default location for the
VTune
Profiler
is:
  • On Linux:
    /root/intel/
    vtune
    /projects/[project directory]/r@@@
  • On Windows:
    • VTune
      Profiler
      Results\[project name]\r@@@
      directory in the solution directory (Visual Studio* IDE)
    • %USERPROFILE%\My Documents\
      Profiler
      XE\Projects\[project directory]\r@@@
      directory (Standalone
      VTune
      Profiler
      GUI)
To open a result from the standalone GUI, select
Open > Result...
from the menu and browse to the result file. To open a result from Visual Studio, double-click the node in the Solution Explorer.

Analysis Configuration Files

File Type
File Location
Preset analysis type (for example,
hotspots.cfg
)
config/analysis_type
in the product installation directory.
Custom analysis type (for example,
Hardware Event-based Sampling Analysis @@@.cfg
, where
@@@
is the next available number)
Windows:
%APPDATA%\intel\
Profiler
XE\analysis_type
Linux:
/root/.intel/
vtune
/analysis_type

Project File

File Type
File Location
Project (for example,
*.
vtune
proj
)
The filename is controlled by the system. However, the file location is controlled by the user. The default location is:
  • On Linux:
    /root/intel/
    vtune
    /projects/[project directory]
  • On Windows:
    • VTune
      Profiler
      Results\[project name]
      directory in the solution directory (Visual Studio* IDE)
    • Profiler
      XE\Projects\[project directory]
      directory (Standalone
      Intel VTune
      Profiler
      GUI)
Examples
Run the Hotspots analysis and then run the Threading analysis. If you use the default naming convention and result location, the
VTune
Profiler
names and saves the results in the following manner:
  • Standalone GUI Linux:
    • /root/intel/
      vtune
      /projects/r000hs/r000hs.
      vtune
    • /root/intel/
      vtune
      /projects/r001tr/r001tr.
      vtune
  • Standalone GUI Windows:
    • %USERPROFILE%\My Documents\
      Profiler
      XE\Projects\[project directory]\r000hs\r000hs.
      vtune
    • %USERPROFILE%\My Documents\
      Profiler
      XE\Projects\[project directory]\r001tr\r001tr.
      vtune
  • Visual Studio IDE:
    • VTune
      Profiler
      Results\[project name]\r000hs\r000hs.
      vtune
    • VTune
      Profiler
      Results\[project name]\r001tr\r000tr.
      vtune
where
  • hs
    is the Hotspots analysis type
  • tr
    is the Threading analysis type

Product and Performance Information

1

Intel's compilers may or may not optimize to the same degree for non-Intel microprocessors for optimizations that are not unique to Intel microprocessors. These optimizations include SSE2, SSE3, and SSSE3 instruction sets and other optimizations. Intel does not guarantee the availability, functionality, or effectiveness of any optimization on microprocessors not manufactured by Intel. Microprocessor-dependent optimizations in this product are intended for use with Intel microprocessors. Certain optimizations not specific to Intel microarchitecture are reserved for Intel microprocessors. Please refer to the applicable product User and Reference Guides for more information regarding the specific instruction sets covered by this notice.

Notice revision #20110804