ARM HPC tools analyze how HPC software runs. It consists of three applications, ARM DDT, ARM Performance Reports and ARM MAP:
- ARM DDT: graphical debugger for HPC applications.
- ARM MAP: HPC application profiler with easy-to-use GUI environment.
- ARM Performance Reports: simple tool to generate a single-page HTML or plain text report that presents overall performance characteristics of HPC applications.
Availability & Restrictions
The following versions of ARM HPC tools are available on OSC clusters:
You can use
module spider arm to view available modules for a given machine. Feel free to contact OSC Help if you need other versions for your work.
ARM DDT, MAP and Performance Reports are available to all OSC users.
ARM DDT is a debugger for HPC software that automatically alerts users of memory bugs and divergent behavior. For more features and benefits, visit ARM HPC tools and libraries - DDT.
For usage instructions and more iformation, read ARM DDT.
ARM MAP produces a detailed profile of HPC software. Unlike ARM Performance Reports, you must have the source code to run ARM MAP because its analysis details the software line-by-line. For more features and benefits, visit ARM HPC tools and libraries - MAP.
For usage instructions and more information, read ARM MAP.
ARM Performance Reports
ARM Performance Reports analyzes and documents information on CPU, MPI, I/O, and Memory performance characteristics of HPC software, even third party code, to aid understanding about the overall performance. Although it should not be used all the time, ARM Performance Reports is recommended to OSC users as a viable option to analyze how an HPC application runs. View an example report to navigate the format of a typical report. For more example reports, features and benefits, visit ARM HPC tools and libraries - Performance Reports.
For usage instructions and more information, read ARM Performance Reports.
Using ARM software with MVAPICH2
This note from ARM's Getting Started Guide applies to both perf-report and MAP:
Some MPIs, most notably MVAPICH, are not yet supported by ARM's Express Launch mode
(in which you can just put “perf-report” in front of an existing mpirun/mpiexec line). These can
still be measured using the Compatibility Launch mode.
Instead of this Express Launch command:
perf-report mpiexec <mpi args> <program> <program args> # BAD
Use the compatibility launch version instead:
perf-report -n <num procs> --mpiargs="<mpi args>" <program> <program args>