- Infos im HLRS Wiki sind nicht rechtsverbindlich und ohne Gewähr -
- Information contained in the HLRS Wiki is not legally binding and HLRS is not responsible for any damages that might result from its use -
Threadspotter: Difference between revisions
From HLRS Platforms
Jump to navigationJump to search
No edit summary |
No edit summary |
||
| Line 25: | Line 25: | ||
== Examples == | == Examples == | ||
=== | === Starting on the nodes interactively === | ||
Set up the environment | |||
{{Command| command = | |||
qsub -I -X ... | |||
module load performance/acumem/threadspotter | |||
acumem | |||
}} | |||
=== Collecting traces automatically from scripts === | |||
Set up the environment | Set up the environment | ||
Revision as of 18:13, 1 February 2011
| RogueWave (formerly Acumem) ThreadSpotter analyses the application on a binary level (your optimized code compiled with debugging symbols, aka {{{-O2 -g}}}), finding occurrences of inefficient memory access patterns, such as cache usage and cache-effects due to multiple threads. The strength of the tool is in the reporting of problematic source code, giving hints in the code, proposing changes and offering information, how the change may affect cache usage. |
| ||||||||||||
Usage
Threadspotter is available through modules
module load performance/acumem
Note: Do not forget to compile your application with debugging info (-g option).
Note: Please note, that for the graphical user interface (GUI), please submit Your interactive session with X11 forwarding: {{{qsub -I -X ...}}}
Examples
Starting on the nodes interactively
Set up the environment
qsub -I -X ...
module load performance/acumem/threadspotter
acumem
Collecting traces automatically from scripts
Set up the environment
module load performance/acumem/threadspotter
Special Information: Nec Nehalem Cluster
XXX
Special Information: Cray XE6
XXX