Version System A System B System C
20.03.0 +
7.1.1 +
7.0.6 + (default)
7.0.4 +
7.0.0 +
6.5.2 +
6.5.1 +
6.4.6 +
6.4.3 +
6.4.1 +

+ = Available for use
― = Not available

Version Modulefile Name
7.0.6 perftools/7.0.6
7.0.4 perftools/7.0.4
7.0.0 perftools/7.0.0
6.5.2 perftools/6.5.2
6.5.1 perftools/6.5.1
6.4.6 perftools/6.4.6
6.4.3 perftools/6.4.3
6.4.1 perftools/6.4.1

Execute the module command as shown below. If the slash (/) and the version in the modulefile are omitted, the default version listed above will be set.

$ module load perftools-base
$ module load perftools

For details on the module command, see Modules.

Commands Purpose
pat_build Converts the executable file to Pat binary for using in CrayPat.
pat_report Generates a report in a text format from a log file made by executing Pat binary.
app2 Displays performance information gathering with CrayPat in the GUI.
pat_help Displays Help information of CrayPat.

Options Purpose
-O apa Sets tracing information automatically.
-g tracegroup Specifies the groups(e.g., mpi, omp) for tracing. For details on specifiable groups, see online manual.

Options Purpose
-T Sets a threshold value as a display target to zero, and enables undisplayable parts by default to be displayed.
-o outputfile Specifies output information. By default, “profile”(display a function name) is specified. For details on specifiable output information, see online manual.

When using CrayPat, preparing an object file( .o) and a library file( .a) is required. The example below shows how to generate an object file and an executable file from a Fortran source file “test.f”.

$ ftn -c test.f
$ ftn -o a.out test.o

To convert “a.out” to Pat binary, use the pat_build command. By default, pat binary “executable fime name+pat” is generated after conversion.

$ pat_build -O apa ./a.out
$ ls
a.out  a.out+pat  test.f  test.o 

Please execute Pat binary as a basic program. For procedures, see Batch Processing(For System A). Executing the Pat binary creates a folder with the name of the executable file name + pat+{PID}-{nodeID}s and outputs the result file under it.

$ qsub
$ ls
a.out  a.out+pat a.out+pat a.out+pat+{PID}-{nodeID}s/  test.f  test.o 

By using the Pat_report command, a Pat report from the xf files saved under the execution file name + pat+{PID}-{nodeID}s/xf-files/ at the time of Pat binary execution. For the ap2 file to be displayed by Apprentice2, it will be created in the executable file name + pat+{PID}-{nodeID}s/ap2-files/{PID}.ap2 .

$ pat_report -o {report name} execution file name+pat+{PID}-{nodeID}s/
e.g.) $ pat_report -o sampling.txt a.out+pat+266817-1646s/ 

$ cat sampling.txt
CrayPat/X:  Version 7.0.6 Revision 22b69ce  02/11/19 21:00:22
Number of PEs (MPI ranks):    1
Numbers of PEs per Node:      1
Numbers of Threads per PE:    1
Number of Cores per Socket:  68

Currently Cray Apprentice2 6.4.3 and later don't work on Excced onDemand (Segmentation Fault). Instead, they work on FastX.

In the X-Windows(GUI) environment(e.g., Exceed onDemand), Cray Apprentice2 enables users to find the profiling result file named “executable file name+pat+XXXXX-XXXX.ap2” generated by the pat_report command.

To use Cray Apprentice2, use the app2 command.

$ app2 executable file name + pat+{PID}-{nodeID}s/ap2-files/{PID}.ap2

The exposition “CrayPatによる性能解析” published in ACCM Bulletin(Inter-University Services) Vol. 12, No. 1 on page 13 *Japanese Version Only

Copyright © Academic Center for Computing and Media Studies, Kyoto University, All Rights Reserved.