• 06/18/2020
  • Public Content

Analyze Performance on Cray* Systems

This section describes how to use
Intel® Advisor
to collect and analyze performance data from an application that runs on a Cray* system. You’ll start by building the application and setting up the Intel Advisor environment on the Cray system. Afterwards, you’ll collect performance data with the
Intel Advisor
command line interface (CLI), save your data as a snapshot, then interpret those results using the
Intel Advisor
GUI on a local system.


This section lists the hardware and software used to produce the specific result shown in this recipe:


On the Cray system:
  1. Set up the programming environment.
    • Make sure the Intel programming environment is loaded by default:
      $ module list
    • If the Cray programming environment is loaded instead, swap the programming environments:
      $ module swap PrgEnv-cray PrgEnv-intel
  2. Clone the application from and expand the compressed file:
    $ tar xzvf ./miniFE-2.2.0.tar.gz
  3. Change directory to the openmp version directory:
    $ cd ./miniFE-2.2.0/openmp/src
  4. Edit the
    file and add the
    option to the CFLAGS definition:
    CFLAGS = -g –O3 -qopenmp
    If you use the Cray ftn or cc compiler wrappers instead of the Intel C++ compiler, you must add the
    option. ftn also detects OpenMP* pragmas, so no openMP* options are required.
On a local system: Set up the
Intel Advisor
in the usual manner.

Build the Application on the Cray System

On the Cray system: Build the application and save the resulting executable in the current directory:
$ make –f ./

Collect Performance Data on the Cray System Using the
Intel Advisor

On the Cray system:
  1. Start an interactive session.
    Use the Slurm scheduler and enable the interactive session using the
    command. For example: Launch a 30-minute interactive session on a single node, in a partition (queue) named debug:
    $ salloc -N 1 -p debug -t 30:00
    A prompt change reflects the new node name after the allocation is granted.
    Some Cray systems connect to a service node (also known as a MOM node) after the allocation becomes active. If this occurs, change directory again to the openmp version directory.
  2. Set up the
    Intel Advisor
    • At this time, there is no homogeneous naming scheme for the
      Intel Advisor
      Cray module. Check your system documentation for the correct name. This recipe uses
      as a convenient placeholder:
      $ module swap PrgEnv-cray PrgEnv-intel $ module load advisor
    • If your center does not have a module, source the
      Intel Advisor
      setup variables in the usual manner:
      $ source <advisor_install_dir>/
    • It may also be necessary to add the library location:
      $ export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/opt/intel/advisor/lib64
  3. Set the number of threads for the
    Intel Advisor
    Survey analysis:
    $ export OMP_NUM_THREADS=32
  4. Run the
    Intel Advisor
    Survey analysis and store the result in the
    $ srun –n 1 –c 32 advixe-cl --collect=survey --project-dir=./adv -- ./miniFE.x

Create an
Intel Advisor
Snapshot on the Cray System to Enable Data Interpretation on a Local System

Intel Advisor
snapshots are an excellent transferral method if post-processing nodes that enable VNC or X11 tunneling connections are unavailable.
On the Cray system:
  1. Generate a read-only snapshot to package all necessary performance data for further investigation in an
    file in the current directory:
    $ advixe-cl --snapshot --project-dir=./adv --pack --cache-sources --cache-binaries -- adv_snapshot
  2. Copy the
    file to a local system using your prefer data transfer method.

Interpret Performance Data on a Local System Using the
Intel Advisor

On the local system: Double-click the snapshot to launch the
Intel Advisor
GUI, and open the
report to display the collected performance data.
Expected result for the miniFE miniapp: This is a poor implementation, with no vectorized code sections and a compilation that did not use the best available Instruction Set Architecture (ISA).

Alternative Steps

Collect Performance Data on the Cray System in Batch Mode (Instead of Interactively)
  1. Create a submission script with all the configuration details. For example: Create a script named
    with the following sample contents:
    #!/bin/bash #SBATCH --job-name=run_name #SBATCH -N 1 #SBATCH -p debug #SBATCH --ntasks-per-node=1 #SBATCH --time=00:30:00 cd $PBS_O_WORKDIR export OMP_NUM_THREADS=32 module swap PrgEnv-cray PrgEnv-intel module load advisor srun –n 1 –c 32 advixe-cl --collect=survey --project-dir=./results_dir -- ./miniFE.x
  2. Submit the script to the scheduler from a login node:
    $ sbatch ./run.slurm
Interpret Performance on the Cray System Using an
Intel Advisor
CLI Text Report (Instead of on a Local System Using a Snapshot and the
Intel Advisor
Generate a summary report that prints to screen:
$ module swap PrgEnv-cray PrgEnv-intel $ module load advisor $ advixe-cl --report=summary --project-dir=./adv --format=text
You can also save report output directly to file and in other formats, such as CSV and XML.

Key Take-Aways

  • It is possible to run the
    Intel Advisor
    on a Cray system if the Cray environment is set up correctly.
  • Creating a snapshot is a good way to move an
    Intel Advisor
    result to a local system that may be more responsive for interactive tasks.

Product and Performance Information


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