User Guide

Contents

Problem:
VTune
Profiler
is Slow to Respond When Collecting or Displaying Data

This problem is specific to Linux* targets.

Cause

  • If your project directory (and consequently, the result files) are located on an NFS-mounted directory and not on a local disk, this significantly impacts performance of the tool in several areas: writing of the results is slower, updating project information is slower, and when loading the results for display you may see delays of several minutes.
  • If application binaries are on an NFS-mounted drive but not on a local drive, the
    VTune
    Profiler
    takes longer to parse symbol information and present the results.

Solution

Make sure your project directory (and consequently, the result files) and application binaries are located on a local disk and not an NFS-mounted directory. By default, the projects are stored in
$HOME/intel/
vtune
/projects
. If your home directory is on an NFS-mounted drive to facilitate access from multiple systems, you should ensure that you set the project directory to a local directory at project creation.

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