Lo2s - Revision history

Thomas-ilsche-b0e0@tu-dresden.de: /* lo2s - Lightweight Node-level Performance Monitoring */

2019-10-04T13:42:39Z

lo2s - Lightweight Node-level Performance Monitoring

Thomas-ilsche-b0e0@tu-dresden.de at 13:06, 4 October 2019

2019-10-04T13:06:24Z

Thomas-ilsche-b0e0@tu-dresden.de: Created page with "= `lo2s` - Lightweight Node-level Performance Monitoring = `lo2s` creates parallel OTF2 traces with a focus on both application and system view. The tra..."

2019-10-04T13:05:56Z

Created page with "= <code>lo2s</code> - Lightweight Node-level Performance Monitoring = <code>lo2s</code> creates parallel OTF2 traces with a focus on both application and system view. The tra..."

New page

= <code>lo2s</code> - Lightweight Node-level Performance Monitoring =

<code>lo2s</code> creates parallel OTF2 traces with a focus on both application and system view. The traces can contain any of the following information:

* From running threads
** Calling context samples based on instruction overflows
** The calling context samples are annotated with the disassembled assembler instruction string
** The framepointer-based call-path for each calling context sample
** Per-thread performance counter readings
** Which thread was scheduled on which CPU at what time
* From the system
** Metrics from tracepoints (e.g. the selected C-state or P-state)
** The node-level system tree (cpus (HW-threads), cores, packages)
** CPU power measurements (x86_energy)
** Microarchitecture specific metrics (x86_adapt, per package or per core)
** Arbitrary metrics through plugins (Score-P compatible)

In general <code>lo2s</code> operates either in '''process monitoring''' or '''system monitoring''' mode.

With '''process monitoring''', all information is grouped by each thread of a monitored process group - it shows you ''on which CPU is each monitored thread running''. <code>lo2s</code> either acts as a prefix command to run the process (and also tracks its children), or <code>lo2s</code> attaches to a running process.

In the '''system monitoring''' mode, information is grouped by logical CPU - it shows you ''which thread was running on a given CPU''. Metrics are also shown per CPU.

In both modes, system-level metrics (e.g. tracepoints), are always grouped by their respective system hardware component.

@@ Line 1: / Line 1: @@
 = <code>lo2s</code> - Lightweight Node-level Performance Monitoring =
-<code>lo2s</code> is available on https://github.com/tud-zih-energy/lo2s
+<code>lo2s</code> is available as open source at https://github.com/tud-zih-energy/lo2s
 <code>lo2s</code> creates parallel OTF2 traces with a focus on both application and system view. The traces can contain any of the following information:

← Older revision		Revision as of 13:06, 4 October 2019
Line 1:		Line 1:
	= <code>lo2s</code> - Lightweight Node-level Performance Monitoring =		= <code>lo2s</code> - Lightweight Node-level Performance Monitoring =
		+
		+	<code>lo2s</code> is available on https://github.com/tud-zih-energy/lo2s

	<code>lo2s</code> creates parallel OTF2 traces with a focus on both application and system view. The traces can contain any of the following information:		<code>lo2s</code> creates parallel OTF2 traces with a focus on both application and system view. The traces can contain any of the following information:

Lo2s - Revision history

Thomas-ilsche-b0e0@tu-dresden.de: /* lo2s - Lightweight Node-level Performance Monitoring */

Thomas-ilsche-b0e0@tu-dresden.de at 13:06, 4 October 2019

Thomas-ilsche-b0e0@tu-dresden.de: Created page with "= lo2s - Lightweight Node-level Performance Monitoring = lo2s creates parallel OTF2 traces with a focus on both application and system view. The tra..."

Thomas-ilsche-b0e0@tu-dresden.de: Created page with "= `lo2s` - Lightweight Node-level Performance Monitoring = `lo2s` creates parallel OTF2 traces with a focus on both application and system view. The tra..."