% IMPORTANT: The following is UTF-8 encoded. This means that in the presence
% of non-ASCII characters, it will not work with BibTeX 0.99 or older.
% Instead, you should use an up-to-date BibTeX implementation like “bibtex8” or
% “biber”.
@MISC{Feld:1037708,
author = {Feld, Christian and Jäkel, René and Lorenz, Daniel and
Wesarg, Bert and Schmidl, Dirk and Tschüter, Ronny and
Oleynik, Yury and Wagner, Michael and Eschweiler, Dominic
and Spazier, Johannes and Knüpfer, Andreas and Shende,
Sameer and Millstein, Suzanne and Biersdorff, Scott and
Geimer, Markus and Schlütter, Marc and Schmitt, Felix and
Ziegenbalg, Johannes and Zhukov, Ilya and Dietrich, Robert
and Geyer, Robin and Saviankou, Pavel and Knobloch, Michael
and Mijaković, Robert and Schöne, Robert and Winkler,
Frank and Ilsche, Thomas and Hermanns, Marc-André and
Brendel, Ronny and Oeste, Sebastian and Herold, Christian
and Sigl, Severin and Hilbrich, Tobias and Williams, Bill
and Klotz, Sven and Corbin, Gregor and Reuter, Jan André
and Grund, Alexander and Sander, Maximilian and Frenzel,
Jan},
title = {{S}core-{P}: {S}calable performance measurement
infrastructure for parallel codes (v8.4); 8.4},
reportid = {FZJ-2025-00868},
year = {2024},
abstract = {The instrumentation and measurement framework Score-P,
together with analysis tools build on top of its output
formats, provides insight into massively parallel HPC
applications, their communication, synchronization, I/O, and
scaling behaviour to pinpoint performance bottlenecks and
their causes. Score-P is a highly scalable and easy-to-use
tool suite for profiling (summarizing program execution) and
event tracing (capturing events in chronological order) of
HPC applications. The scorep instrumentation command adds
instrumentation hooks into a user's application by either
prepending or replacing the compile and link commands. C,
C++, Fortran, and Python codes as well as contemporary HPC
programming models (MPI, threading, GPUs, I/O) are
supported. When running an instrumented application,
measurement event data is provided by the instrumentation
hooks to the measurement core. There, the events are
augmented with high-accuracy timestamps and potentially
hardware counters (a plugin-API allows querying additional
metric sources). The augmented events are then passed to one
or both of the built-in event consumers, profiling and
tracing (a plugin-API allows creation of additional event
consumers) which finally provide output in the formats CUBE4
and OTF2, respectively. Score-P is available under the
3-clause BSD Open Source license.},
keywords = {Performance measurement (Other) / Score-P (Other) /
instrumentation (Other) / sampling (Other) / HPC (Other) /
profiling (Other) / tracing (Other)},
cin = {JSC},
cid = {I:(DE-Juel1)JSC-20090406},
pnm = {5112 - Cross-Domain Algorithms, Tools, Methods Labs (ATMLs)
and Research Groups (POF4-511)},
pid = {G:(DE-HGF)POF4-5112},
typ = {PUB:(DE-HGF)33},
doi = {10.5281/ZENODO.10822140},
url = {https://juser.fz-juelich.de/record/1037708},
}