- Infos im HLRS Wiki sind nicht rechtsverbindlich und ohne Gewähr -

Difference between revisions of "Threadspotter"

From HLRS Platforms
Jump to navigationJump to search
m
Line 5: Line 5:
 
| category    = [[:Category:Debugger | Debugger]]
 
| category    = [[:Category:Debugger | Debugger]]
 
| license      = Commercial
 
| license      = Commercial
| website      = [http://www.roguewave.com/ | Roguewave homepage]  
+
| website      = [http://www.roguewave.com/ Roguewave homepage]
 
}}
 
}}
  

Revision as of 11:38, 18 March 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.
Developer: RogueWave (formely Acumem)
Platforms: NEC Nehalem Cluster, Cray XE6
Category: Debugger
License: Commercial
Website: Roguewave homepage


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


See also

External links