Development/Score-P: Difference between revisions

From bwHPC Wiki
Jump to navigation Jump to search
(Created page with "{| width=600px class="wikitable" |- ! Description !! Content |- | module load | devel/gdb |- | Availability | bwUniCluster | BwForCluster_Chemistry |- | License |...")
 
No edit summary
 
(10 intermediate revisions by 2 users not shown)
Line 1: Line 1:
{{Softwarepage|devel/scorep}}

{| width=600px class="wikitable"
{| width=600px class="wikitable"
|-
|-
Line 4: Line 6:
|-
|-
| module load
| module load
| devel/gdb
| devel/scorep
⚫
|-
| Availability
| [[bwUniCluster]] | [[BwForCluster_Chemistry]]
|-
|-
| License
| License
| [http://www.gnu.org/licenses/ GPL]
| [https://opensource.org/licenses/BSD-3-Clause BSD 3-clause License]
|-
|-
|Citing
|Citing
| A. Knüpfer et al, [http://link.springer.com/chapter/10.1007%2F978-3-642-31476-6_7 Score-P: A Joint Performance Measurement Run-Time Infrastructure for Periscope, Scalasca, TAU, and Vampir], in Tools for High Performance Computing 2011, pages 79-91, Springer.
| n/a
|-
|-
| Links
| Links
| [http://www.gnu.org/software/gdb/ Homepage] | [http://www.gnu.org/software/gdb/documentation/ Documentation] | [https://sourceware.org/gdb/wiki/ Wiki] | [http://www.gnu.org/software/gdb/mailing-lists/ Mailinglists]
| [http://www.vi-hps.org/projects/score-p/ Homepage] | [http://scorepci.pages.jsc.fz-juelich.de/scorep-pipelines/docs/scorep-6.0/html/ Documentation] | [https://mailman.zih.tu-dresden.de/groups/listinfo/scorep-news News Mailinglists] | [mailto:support@score-p.org Bug Reports]
|-
|-
| Graphical Interface
| Graphical Interface
Line 22: Line 21:
|-
|-
| Included modules
| Included modules
⚫
| -
| icc | icpc | ifort | idb
|}
|}
<br>
<br>
= Introduction =
= Introduction =
The Score-P Project is a profiling and tracing library with supportive tools developed mainly by by the [[http://www.vi-hps.org/ VI-HPS]] project.
The '''GNU Debugger (GDB)''' is a standard debugger for serial programs although it can be used for parallel and even distributed programs with few processes too. In the past Intel supported their own '''idb''' debugger, however this has been deprecated in favor of their own port called <kbd>gdb-ia</kbd>.
<br>
<br>


= Versions and Availability =
= Versions and Availability =
A list of versions currently available on all bwHPC-C5-Clusters can be obtained from the
<br>
<big>


[https://cis-hpc.uni-konstanz.de/prod.cis/ Cluster Information System CIS]

⚫
</big>
{{#widget:Iframe
|url=https://cis-hpc.uni-konstanz.de/prod.cis/bwUniCluster/devel/gdb
|width=99%
|height=120
}}
On the command line interface of any bwHPC cluster you'll get a list of available versions
On the command line interface of any bwHPC cluster you'll get a list of available versions
by using the command <kbd>module avail devel/gdb</kbd>.
by using the command <kbd>module avail devel/scorep</kbd>.
'''Please note''' that Score-P installation may be ''hidden'' in the sense that it's dependent on the
MPI, which in turn is dependent on the compiler.
So while there are a multitude of compiler version's only some may feature an MPI, which offers tracing using Score-P.
Please use <kbd>module --ignore-cache spider</kbd> to evaluate all possible installations.
<pre>
<pre>
$ : bwUniCluster 2.0
$ : bwUniCluster 2.0
$ module avail devel/gdb
$ module load compiler/gnu/10.2 mpi/openmpi ; module avail devel/score
------------------------ /opt/bwhpc/common/modulefiles/Core -------------------------
------------------------ /opt/bwhpc/common/modulefiles/Core -------------------------
devel/gdb/9.2 devel/gdb/10.1 (D)</pre>
devel/scorep/6.0</pre>


⚫
= Loading =
<font color=red>Attention!</font><br>
Score-P may be loaded with a specific compiler and MPI:
The installed default system GDB may be a different version.
⚫
<pre>$ module load compiler/gnu/10.2 mpi/openmpi devel/scorep</pre>
Check the <font color=green>default</font> version by: <pre>gdb --version</pre> <font color=red>without loaded GDB-module</font>.

Check the installation of this Score-P instance using <kbd>scorep-info</kbd> here with some important output:
<pre>
<pre>
$ scorep-info config-summary
⚫
$ module purge # clear all loaded modules
⚫
...
$ gdb --version # this is the default version
Loaded modules:
GNU gdb (GDB) Red Hat Enterprise Linux 8.2-11.el8
module load compiler/gnu/10.2 \
⚫
[...]
$ module avail devel/gdb # available GDB-module
mpi/openmpi/4.0 \
⚫
devel/cuda/10.2
------------------------ /opt/bwhpc/common/modulefiles/Core -------------------------
...
devel/gdb/9.2 devel/gdb/10.1 (D)</pre>
PAPI support: yes
It is ''not'' recommended to debug MPI-parallel binaries with GDB, please read [[MPI]] on how to do that.
OpenCL support: yes
Rather parallel debuggers like ARM Forge (formerly Allinea ddt) or Totalview ease debugging with a GUI.
libOpenCL support: yes, using -lOpenCL
<br>
...
CUDA support: yes
libcudart support: yes, using -I/opt/bwhpc/common/devel/cuda/10.2/include -L/opt/bwhpc/common/devel/cuda/10.2/lib64 -R/opt/bwhpc/common/devel/cuda/10.2/lib64 -lcudart
libcuda support: yes, using -L/opt/bwhpc/common/devel/cuda/10.2/targets/x86_64-linux/lib/stubs/ -R/opt/bwhpc/common/devel/cuda/10.2/targets/x86_64-linux/lib/stubs/ -lcuda
libcupti support: yes, using -I/opt/bwhpc/common/devel/cuda/10.2/include -I/opt/bwhpc/common/devel/cuda/10.2/extras/CUPTI/include -L/opt/bwhpc/common/devel/cuda/10.2/extras/CUPTI/lib64 -R/opt/bwhpc/common/devel/cuda/10.2/extras/CUPTI/lib64 -lcupti
CUPTI async support: yes
CUDA version >= 6.0: yes
...
OpenMP support: yes, using -fopenmp
OpenMP pomp_tpd: yes
OpenMP ancestry: yes
⚫
</pre>




⚫
= Loading =
It is possible to choose between several versions of GDB. By default both programs are installed. You can check the version which is currently used with:
<pre>$ gcc --version</pre>
<br>
To use a different version ofGDB, you have to load it through the module system.
For example if you need GDB 10.1, load the <kbd>devel/gdb</kbd> module.
<br>
How to load the desired version (e.g. GDB version 9.2):
⚫
<pre>$ module load devel/gdb/9.2</pre>
<br>
<br>



= Documentation =
= Documentation =
For '''online documentation''' see the links section in the summary table at the top of this page. For '''local documentation''' consult the man page.
For '''online documentation''' see the links section in the summary table at the top of this page.
For '''local documentation''' please check the manual below the <kbd>$SCOREP_DOC_DIR</kbd> directory using a browser to:
<pre>$ man gdb</pre>
<br>
<pre>
firefox $SCOREP_DOC_DIR/scorep/html/

</pre>


The man pages added are for the (sub-project) PAPI, i.e. the CPU performance counters.
[[Category:Performance analysis software]][[Category:bwUniCluster]]

Latest revision as of 13:22, 9 August 2024

The main documentation is available via module help devel/scorep on the cluster. Most software modules for applications provide working example batch scripts.


Description Content
module load devel/scorep
License BSD 3-clause License
Citing A. Knüpfer et al, Score-P: A Joint Performance Measurement Run-Time Infrastructure for Periscope, Scalasca, TAU, and Vampir, in Tools for High Performance Computing 2011, pages 79-91, Springer.
Links Homepage | Documentation | News Mailinglists | Bug Reports
Graphical Interface No
Included modules -


Introduction

The Score-P Project is a profiling and tracing library with supportive tools developed mainly by by the [VI-HPS] project.

Versions and Availability

On the command line interface of any bwHPC cluster you'll get a list of available versions by using the command module avail devel/scorep. Please note that Score-P installation may be hidden in the sense that it's dependent on the MPI, which in turn is dependent on the compiler. So while there are a multitude of compiler version's only some may feature an MPI, which offers tracing using Score-P. Please use module --ignore-cache spider to evaluate all possible installations. 

$ : bwUniCluster 2.0
$ module load compiler/gnu/10.2 mpi/openmpi ; module avail devel/score
------------------------ /opt/bwhpc/common/modulefiles/Core -------------------------
devel/scorep/6.0

Loading

Score-P may be loaded with a specific compiler and MPI: 

$ module load compiler/gnu/10.2 mpi/openmpi devel/scorep

Check the installation of this Score-P instance using scorep-info here with some important output: 

$ scorep-info config-summary
...
Loaded modules:
  module load                   compiler/gnu/10.2 \
                                mpi/openmpi/4.0 \
                                devel/cuda/10.2
...
      PAPI support:             yes
      OpenCL support:           yes
        libOpenCL support:      yes, using -lOpenCL
...
      CUDA support:             yes
        libcudart support:      yes, using -I/opt/bwhpc/common/devel/cuda/10.2/include -L/opt/bwhpc/common/devel/cuda/10.2/lib64 -R/opt/bwhpc/common/devel/cuda/10.2/lib64 -lcudart
        libcuda support:        yes, using -L/opt/bwhpc/common/devel/cuda/10.2/targets/x86_64-linux/lib/stubs/ -R/opt/bwhpc/common/devel/cuda/10.2/targets/x86_64-linux/lib/stubs/ -lcuda
        libcupti support:       yes, using -I/opt/bwhpc/common/devel/cuda/10.2/include -I/opt/bwhpc/common/devel/cuda/10.2/extras/CUPTI/include -L/opt/bwhpc/common/devel/cuda/10.2/extras/CUPTI/lib64 -R/opt/bwhpc/common/devel/cuda/10.2/extras/CUPTI/lib64 -lcupti
        CUPTI async support:    yes
        CUDA version >= 6.0:    yes
...
      OpenMP support:           yes, using -fopenmp
        OpenMP pomp_tpd:        yes
        OpenMP ancestry:        yes



Documentation

For online documentation see the links section in the summary table at the top of this page. For local documentation please check the manual below the $SCOREP_DOC_DIR directory using a browser to: 

firefox $SCOREP_DOC_DIR/scorep/html/

The man pages added are for the (sub-project) PAPI, i.e. the CPU performance counters.

Retrieved from "https://wiki.bwhpc.de/wiki/index.php?title=Development/Score-P&oldid=12886"