Differences

This shows you the differences between two versions of the page.

--- skill-tree:pe:2:2:b [2020/06/18 20:15] – external edit 127.0.0.1
+++ skill-tree:pe:2:2:b [2021/09/13 11:57] (current) – external edit 127.0.0.1
@@ Line 1: / Line 1: @@
 # PE2.2-B Profiling
 # Background
-  *  Profiling is explained for the CPU level, where it can be supported by hardware performance counters and by sampling techniques.
-  *  Sampling is used to see, by examining the program counter, what routines and source code lines of a program are responsible for which portions of the total runtime.
+Profiling is explained for the CPU level, where it can be supported by hardware performance counters and by sampling techniques.
-  *  Automatically adding trace code to a parallel program by so-called instrumentation to record its execution in a strict chronology is explained and the difference to profiling is emphasized.
-  *  Similar techniques are explained for profiling the network level (e.g. based on InfiniBand counters and I/O server states).
+Sampling is used to see, by examining the program counter, what routines and source code lines of a program are responsible for which portions of the total runtime.
+Automatically adding trace code to a parallel program by so-called instrumentation to record its execution in a strict chronology is explained and the difference to profiling is emphasized.
+Similar techniques are explained for profiling the network level (e.g. based on InfiniBand counters and I/O server states).
 # Aim
 # Outcomes
-  *  detect performance issues and bottlenecks caused, for example, by inefficient programming, memory accesses, I/O operations, cache-misses, page-faults, and parallelization overheads
+  * Detect performance issues and bottlenecks caused, for example, by inefficient programming, memory accesses, I/O operations, cache-misses, page-faults, and parallelization overheads.
-  *  use environment variables like $I_MPI_STATS to control the built-in performance analysis functionality in MPI
+  * Use environment variables like $I_MPI_STATS to control the built-in performance analysis functionality in MPI.
 # Subskills
+  * [[skill-tree:pe:2:2:2:b]]
   * [[skill-tree:pe:2:2:1:b]]
+  * [[skill-tree:pe:2:2:i]]
+  * [[skill-tree:pe:2:2:e]]