Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
hpc-compendium
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Deploy
Releases
Package Registry
Container Registry
Model registry
Operate
Terraform modules
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
ZIH
hpcsupport
hpc-compendium
Merge requests
!391
Adds HPC entry for lo2s
Code
Review changes
Check out branch
Download
Patches
Plain diff
Merged
Adds HPC entry for lo2s
lo2s-entry
into
preview
Overview
1
Commits
6
Pipelines
0
Changes
1
Merged
Mario Bielert
requested to merge
lo2s-entry
into
preview
3 years ago
Overview
1
Commits
6
Pipelines
0
Changes
1
Expand
Fixes
#47 (closed)
1
0
Merge request reports
Viewing commit
11f775ca
Prev
Next
Show latest version
1 file
+
14
−
14
Inline
Compare changes
Side-by-side
Inline
Show whitespace changes
Show one file at a time
11f775ca
Fix minor issues
· 11f775ca
Martin Schroschk
authored
3 years ago
doc.zih.tu-dresden.de/docs/software/lo2s.md
+
14
−
14
Options
#
`
lo2s
`
- Lightweight Node-Level Performance Monitoring
# lo2s - Lightweight Node-Level Performance Monitoring
`lo2s`
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 frame pointer-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 core)
*
Arbitrary metrics through plugins (Score-P compatible)
*
From running threads
*
Calling context samples based on instruction overflows
*
The calling context samples are annotated with the disassembled assembler instruction string
*
The frame pointer-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 core)
*
Arbitrary metrics through plugins (Score-P compatible)
In general,
`lo2s`
operates either in
**process monitoring**
or
**system monitoring**
mode.
@@ -119,7 +119,7 @@ marie@compute$ lo2s -a -- sleep 10
```
Like in the
`process monitoring mode`
,
`lo2s`
can also sample instructions in the system monitoring mode.
You can enable the instruction sampling by passing the
`--instruction-sampling`
parameter
to
`lo2s`
.
You can enable the instruction sampling by passing the
parameter
`--instruction-sampling`
to
`lo2s`
.
```
console
marie@compute$
lo2s
-a
--instruction-sampling
--
make
-j
Loading