Several performance tools co-exist

Several performance tools co-exist

• Several performance tools co-exist

• Separate measurement systems and output formats

• Complementary features and overlapping functionality

• Redundant effort for development and maintenance

• Limited or expensive interoperability

• Complications for user experience, support, training

Start a community effort for a common infrastructure

• Start a community effort for a common infrastructure

• Score-P instrumentation and measurement system
• Common data formats OTF2 and CUBE4

• Developer perspective:

• Save manpower by sharing development resources
• Invest in new analysis functionality and scalability
• Save efforts for maintenance, testing, porting, support, training

• User perspective:

• Single learning curve
• Single installation, fewer version updates
• Interoperability and data exchange

• SILC project funded by BMBF

• Close collaboration PRIMA project funded by DOE

Forschungszentrum Jülich, Germany

• Forschungszentrum Jülich, Germany

• German Research School for Simulation Sciences, Aachen, Germany

• Gesellschaft für numerische Simulation mbH Braunschweig, Germany

• RWTH Aachen, Germany

• Technische Universität Dresden, Germany

• Technische Universität München, Germany

• University of Oregon, Eugene, USA

Provide typical functionality for HPC performance tools

• Provide typical functionality for HPC performance tools

• Support all fundamental concepts of partner’s tools

• Instrumentation (various methods)

• Flexible measurement without re-compilation:

• Basic and advanced profile generation
• Event trace recording
• Online access to profiling data

• MPI, OpenMP, and hybrid parallelism (and serial)

• Enhanced functionality (OpenMP 3.0, CUDA, highly scalable I/O)

Functional requirements

• Functional requirements

• Generation of call-path profiles and event traces
• Using direct instrumentation, later also sampling
• Recording time, visits, communication data, hardware counters
• Access and reconfiguration also at runtime
• Support for MPI, OpenMP, basic CUDA, and all combinations
• Later also OpenCL/HMPP/PTHREAD/…

• Non-functional requirements

• Portability: all major HPC platforms
• Scalability: petascale
• Low measurement overhead
• Easy and uniform installation through UNITE framework
• Robustness
• Open Source: New BSD License

Scalability to maximum available CPU core count

• Scalability to maximum available CPU core count

• Support for OpenCL, HMPP, PTHREAD

• Support for sampling, binary instrumentation

• Support for new programming models, e.g., PGAS

• Support for new architectures

• Ensure a single official release version at all times which will always work with the tools

• Allow experimental versions for new features or research

• Commitment to joint long-term cooperation

Can be used to mark initialization, solver & other phases

• Can be used to mark initialization, solver & other phases

• Annotation macros ignored by default
• Enabled with [--user] flag

• Appear as additional regions in analyses

• Distinguishes performance of important phase from rest

• Can be of various type

• E.g., function, loop, phase
• See user manual for details

• Available for Fortran / C / C++

• Requires processing by the C preprocessor

Can be used to temporarily disable measurement for certain intervals

• Can be used to temporarily disable measurement for certain intervals

• Annotation macros ignored by default
• Enabled with [--user] flag

Score-P

• Score-P

• Community instrumentation & measurement infrastructure
• Instrumentation (various methods)
• Basic and advanced profile generation
• Event trace recording
• Online access to profiling data
• Available under New BSD open-source license
• Documentation & Sources:
• http://www.score-p.org
• User guide also part of installation:
• 
  /share/doc/scorep/{pdf,html}/
• Contact: [e-mail]
• Bugs: [e-mail]