- 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 -
Paraver: Difference between revisions
From HLRS Platforms
Jump to navigationJump to search
(→Usage) |
(→Usage) |
||
Line 17: | Line 17: | ||
}} | }} | ||
Then you can start it | Then you can start it with | ||
{{Command|command = | {{Command|command = | ||
wxparaver | wxparaver | ||
}} | |||
{{Warning|text = | |||
When working with large traces please use a compute node. | |||
}} | }} | ||
Revision as of 10:07, 15 November 2017
Based on an easy-to-use Motif GUI, Paraver was developed to respond to the need to have a qualitative global perception of the application behavior by visual inspection and then to be able to focus on the detailed quantitative analysis of the problems. Paraver provides a large amount of information useful to improve the decisions on whether and where to invert the programming effort to optimize an application. |
|
Usage
To use Paraver load the respective software module:
module load performance/paraver
Then you can start it with
wxparaver
Warning: When working with large traces please use a compute node.
Note: Do not forget to enable X forwarding when logging in using the -X options for ssh and qsub.