• 9.1
  • 07/08/2015
  • Public Content

Generate a Trace File


To check how the configuration file influences the trace collection process, run four processes of the
poisson
sample code with the following configuration file:
  1. Create a new configuration file.
  2. Type in the following parameters:
    LOGFILE-FORMAT STFSINGLE ACTIVITY MPI OFF STATE MPI:*Allreduce* ON
  3. Save the configuration file, for example,
    filter.conf.
  4. Set the
    VT_CONFIG
    environment variable to the directory that contains the configuration file:
    VT_CONFIG=/<
    path_name
    >/filter.conf
  5. Run the application.
    Linux* OS:
    $ mpirun -trace -n 4 ./poisson
    Windows* OS:
    > mpiexec -n 4 poisson.exe
To check the results, do the following:
Check your work:
  1. Open the resulting trace file in Intel® Trace Analyzer.
  2. In the Function Profile, right-click
    Group MPI
    and select
    Ungroup Group MPI
    from the context menu.
  3. Go to the
    Load Balance
    tab of the Function Profile to see how the function is distributed among the four processes.
  4. Go to
    Charts > Event Timeline
    to see the activities in each of the four processes individually.
The result looks like:
You can see that the trace data was collected only for the function.
Key Terms

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