Skip to content
Snippets Groups Projects

Running applications

Merged Adam Caprez requested to merge running-applications into master
41 files
+ 5364
16608
Compare changes
  • Side-by-side
  • Inline
Files
41
1. [HCC-DOCS](index.html)
2. [HCC-DOCS Home](HCC-DOCS-Home_327685.html)
3. [HCC Documentation](HCC-Documentation_332651.html)
4. [Running Applications](Running-Applications_7471153.html)
5. [Allinea Profiling & Debugging Tools](16516466.html)
+++
title = "Allinea Performance Reports"
description = "How to use Allinea Performance Reports to profile application on HCC resources."
+++
<span id="title-text"> HCC-DOCS : Allinea Performance Reports </span>
=====================================================================
Created by <span class="author"> Adam Caprez</span>, last modified on
Jul 10, 2015
| Name | Version | Resource |
|---------|---------|----------|
| allinea | 4.2 | tusker |
| allinea | 5.0 | tusker |
| | | |
|---------|-----|-------|
| allinea | 4.2 | crane |
| allinea | 5.0 | crane |
<a href="http://www.allinea.com/products/allinea-performance-reports" class="external-link">Allinea Performance Reports</a> is
a performance evaluation tool that provides a scalable and effective way
[Allinea Performance Reports](https://www.arm.com/products/development-tools/server-and-hpc/performance-reports)
is a performance evaluation tool that provides a scalable and effective way
to understand and analyze the performance of applications executed on
high-performance systems. Allinea Performance Reports can be used with
any application - no source code, recompilation or instrumentation is
@@ -42,7 +23,7 @@ and suggestions of possible application improvements. Allinea
Performance Reports has low runtime overhead of less than 5%.
Using Allinea Performance Reports on HCC
========================================
----------------------------------------
The Holland Computing Center owns **512 Allinea Performance Reports
licenses** that can be used to evaluate applications executed on Tusker
@@ -51,67 +32,63 @@ In order to use Allinea Performance Reports on HCC, the appropriate
module needs to be loaded first. To load the module on Tusker or Crane,
use
| |
|-------------------------|
| module load allinea/5.0 |
{{< highlight bash >}}
module load allinea/5.0
{{< /highlight >}}
Once the module is loaded, Allinea Performance Reports runs by adding
the **perf-report** command in front of the standard application
the `perf-report` command in front of the standard application
command.
Basic Allinea Performance Reports Usage
---------------------------------------
The basic usage of **perf-report** is:
### Basic Allinea Performance Reports Usage
**perf-report usage**
The basic usage of ``perf-report` is:
``` syntaxhighlighter-pre
{{% panel theme="info" header="perf-report usage" %}}
{{< highlight bash >}}
perf-report [OPTION...] PROGRAM [PROGRAM_ARGS]
or
perf-report [OPTION...] (mpirun|mpiexec|aprun|...) [MPI_ARGS] PROGRAM [PROGRAM_ARGS]
```
{{< /highlight >}}
{{% /panel %}}
For example, the command below shows how to run **perf-report** with the
application **hello\_world**:
For example, the command below shows how to run `perf-report` with the
application `hello_world`:
**perf-report example**
``` syntaxhighlighter-pre
{{% panel theme="info" header="perf-report example" %}}
{{< highlight bash >}}
[<username>@login.tusker ~]$ perf-report ./hello-world
```
{{< /highlight >}}
{{% /panel %}}
Stdin redirection
<span
class="aui-icon aui-icon-small aui-iconfont-warning confluence-information-macro-icon"></span>
If your program normally uses the '&lt;' syntax to redirect standard in
{{% notice info %}}
If your program normally uses the '`<`' syntax to redirect standard in
to read from a file, you must use the `--input` option to the
`perf-report `command instead.
{{% /notice %}}
**perf-report stdin redirection**
``` syntaxhighlighter-pre
{{% panel theme="info" header="perf-report stdin redirection" %}}
{{< highlight bash >}}
[<username>@login.tusker ~]$ perf-report --input=my_input.txt ./hello-world
```
{{< /highlight >}}
{{% /panel %}}
Allinea Performance Reports Options
-----------------------------------
### Allinea Performance Reports Options
More **perf-report** options can be seen by using:
**perf-report options**
``` syntaxhighlighter-pre
{{% panel theme="info" header="perf-report options" %}}
{{< highlight bash >}}
[<username>@login.tusker ~]$ perf-report --help
```
{{< /highlight >}}
{{% /panel %}}
Some of the most useful options are:
**perf-report useful options**
``` syntaxhighlighter-pre
{{% panel theme="info" header="perf-report useful options" %}}
{{< highlight bash >}}
--input=FILE (pass the contents of FILE to the target's stdin)
--nompi, --no-mpi (run without MPI support)
--mpiargs=ARGUMENTS (command line arguments to pass to mpirun)
@@ -119,48 +96,21 @@ Some of the most useful options are:
--openmp-threads=NUMTHREADS (configure the number of OpenMP threads for the target)
-n, --np, --processes=NUMPROCS (specify the number of MPI processes)
--procs-per-node=PROCS (configure the number of processes per node for MPI jobs)
```
<span style="line-height: 1.4285715;">
</span>
<span style="line-height: 1.4285715;">The following pages, </span>[Blast
with Allinea Performance
Reports](Blast-with-Allinea-Performance-Reports_11635295.html)<span
style="line-height: 1.4285715;">, </span>[Ray with Allinea Performance
Reports](Ray-with-Allinea-Performance-Reports_11635300.html) and [LAMMPS
with Allinea Performance
Reports](LAMMPS-with-Allinea-Performance-Reports_11635305.html), <span
style="line-height: 1.4285715;">show how to run Allinea Performance
Reports with applications using OpenMP, MPI and standard input/output
respectively.</span>
{{< /highlight >}}
{{% /panel %}}
<span
class="aui-icon aui-icon-small aui-iconfont-warning confluence-information-macro-icon"></span>
**Currently, Allinea Performance Reports works best with compiled
binaries of an application (for some perl/python files perf-report needs
to be added in the actual file).**
Attachments:
------------
<img src="assets/images/icons/bullet_blue.gif" width="8" height="8" />
[cb\_allinea\_module.xsl](attachments/11635289/11635290.xsl)
(application/octet-stream)
<img src="assets/images/icons/bullet_blue.gif" width="8" height="8" />
[crane\_allinea\_version.xsl](attachments/11635289/11635291.xsl)
(application/octet-stream)
<img src="assets/images/icons/bullet_blue.gif" width="8" height="8" />
[crane\_modules.xml](attachments/11635289/11635292.xml)
(application/octet-stream)
<img src="assets/images/icons/bullet_blue.gif" width="8" height="8" />
[tusker\_allinea\_version.xsl](attachments/11635289/11635293.xsl)
(application/octet-stream)
<img src="assets/images/icons/bullet_blue.gif" width="8" height="8" />
[tusker\_modules.xml](attachments/11635289/11635294.xml)
(application/octet-stream)
The following pages
- [Blast with Allinea Performance Reports]({{< relref "blast_with_allinea_performance_reports" >}})
- [Ray with Allinea Performance Reports]({{< relref "ray_with_allinea_performance_reports" >}})
- [LAMMPS with Allinea Performance Reports]({{< relref "lammps_with_allinea_performance_reports" >}})
show how to run Allinea Performance Reports with applications using OpenMP, MPI and standard input/output
respectively.
{{% notice tip %}}
Currently, Allinea Performance Reports works best with compiled
binaries of an application (for some perl/python files perf-report needs
to be added in the actual file).
{{% /notice %}}
Loading