Différences
Ci-dessous, les différences entre deux révisions de la page.
| Les deux révisions précédentes Révision précédente Prochaine révision | Révision précédente | ||
| outils_analyse:hpctoolkit [2016/04/20 13:55] – [Analyze measurements] admin | outils_analyse:hpctoolkit [2016/04/20 14:18] (Version actuelle) – [Links] admin | ||
|---|---|---|---|
| Ligne 48: | Ligne 48: | ||
| </ | </ | ||
| - | Events are passed as arguments of the form --event E_I@P_I, where: | + | Events are passed as arguments of the form '' |
| - | * E_I: event identifier (WALLCLOCK, MEMLEAK, etc); | + | * '' |
| - | * P_1: period in units meaningful to the event: microseconds for WALLCLOCK, cycles for PAPI_TOT_CYC, | + | * '' |
| - | Now we pick a random metric to use, such as the performance of single precision division: | + | For example: |
| <code bash> | <code bash> | ||
| - | $ mpirun -np 16 hpcrun --event | + | $ mpirun -np 16 hpcrun --event |
| </ | </ | ||
| Ligne 66: | Ligne 66: | ||
| ==== Analyze measurements ==== | ==== Analyze measurements ==== | ||
| - | Finally, we combine the measurements with the program structure, obtaining the final profiling database, using the command hpcprof: | + | Finally, we combine the measurements with the program structure, obtaining the final profiling database, using the command |
| <code bash> | <code bash> | ||
| Ligne 73: | Ligne 73: | ||
| </ | </ | ||
| + | |||
| + | The parameter '' | ||
| ==== Display results ==== | ==== Display results ==== | ||
| + | Display results using hpcviewer: | ||
| + | |||
| + | <code bash> | ||
| + | $ hpcviewer hpctoolkit-cpi-database | ||
| + | </ | ||
| + | |||
| + | {{ : | ||
| + | |||
| + | === Tracing === | ||
| + | |||
| + | |||
| + | To get tracing information, | ||
| + | |||
| + | We now point hpctraceviewer to the database folder: | ||
| + | |||
| + | <code bash> | ||
| + | $ hpctraceviewer hpctoolkit-cpi-database | ||
| + | |||
| + | </ | ||
| + | |||
| + | ====== Links ====== | ||
| + | |||
| + | * http:// | ||