PIPER: Difference between revisions
From Modelado Foundation
imported>Schulzm No edit summary |
imported>Schulzm No edit summary |
||
Line 19: | Line 19: | ||
== Objectives == | == Objectives == | ||
Exascale architectures and applications will be much more complex than today's systems, and to achieve high performance, radical changes will be required in high performance computing (HPC) applications and in the system software stack. In such a variable environment, performance tools are essential to enable users to optimize application and system code. Tools must provide online performance feedback to runtime systems to guide online adaptation, and they must output intuitive summaries and visualizations to help developers identify performance problems. | |||
PIPER (Performance Insights for Programmers and Exascale Runtimes) is a multi-institutional collaboration funded under the Office of Science's X-Stack program that targets the development of new techniques for measuring, analyzing, attributing, and presenting performance data on exascale systems. | PIPER (Performance Insights for Programmers and Exascale Runtimes) is a multi-institutional collaboration funded under the Office of Science's X-Stack program that targets the development of new techniques for measuring, analyzing, attributing, and presenting performance data on exascale systems. | ||
Line 29: | Line 31: | ||
[[File:Example.jpg]] | [[File:Example.jpg]] | ||
== Software Stack == | == Interaction with the Software Stack == | ||
We will implement our research in a set of modular components that can be deployed | |||
across various execution and programming models, covering both legacy (MPI+X) models and new models developed in other X-Stack2 projects. Wherever possible, we will leverage the extensive | |||
tool infrastructures available through prior work in our project team and integrate | |||
the results of our research back into these existing production-level tool sets. | |||
Furthermore, we will make the results of our research available to a broad audience | |||
and work with the larger tools community to achieve a wider adaption. | |||
The figure below provides an initial high-level sketch of our envisioned architecture | |||
that will provide the PIPER functionality: | |||
[[File:Example.jpg]] | [[File:Example.jpg]] | ||
We will target measurements from the entire hardware/software stack. That is, | |||
we expect to use measurements from both the underlying system hardware as well | |||
as custom measurements derived from the application. The measurements themselves | |||
will leverage a series of adaptive instrumentation techniques. As part of the | |||
measurement operation, we will associate the measurements with a local | |||
call stack. The correlated local stack/performance measurement data will feed | |||
an analysis pipeline consisting of both node-local analysis methods, and | |||
distributed, wider-context analysis methods. | |||
The resulting data | |||
store will support a high-level query interface used by visualization and data | |||
analysis reporting tools informing the user. Such a system also enables dynamic tuning, | |||
and feedback-directed optimization. |
Revision as of 06:49, September 28, 2013
Description goes here
Team Members
- Lawrence Livermore National Laboratory (team pages)
- Pacific Northwest National Laboratory (team pages)
- Rice University (team pages)
- University of Maryland (team pages)
- University of Utah (team pages)
- University of Wisconsin (team pages)
Objectives
Exascale architectures and applications will be much more complex than today's systems, and to achieve high performance, radical changes will be required in high performance computing (HPC) applications and in the system software stack. In such a variable environment, performance tools are essential to enable users to optimize application and system code. Tools must provide online performance feedback to runtime systems to guide online adaptation, and they must output intuitive summaries and visualizations to help developers identify performance problems.
PIPER (Performance Insights for Programmers and Exascale Runtimes) is a multi-institutional collaboration funded under the Office of Science's X-Stack program that targets the development of new techniques for measuring, analyzing, attributing, and presenting performance data on exascale systems.
Approch
Interaction with the Software Stack
We will implement our research in a set of modular components that can be deployed across various execution and programming models, covering both legacy (MPI+X) models and new models developed in other X-Stack2 projects. Wherever possible, we will leverage the extensive tool infrastructures available through prior work in our project team and integrate the results of our research back into these existing production-level tool sets. Furthermore, we will make the results of our research available to a broad audience and work with the larger tools community to achieve a wider adaption. The figure below provides an initial high-level sketch of our envisioned architecture that will provide the PIPER functionality:
We will target measurements from the entire hardware/software stack. That is, we expect to use measurements from both the underlying system hardware as well as custom measurements derived from the application. The measurements themselves will leverage a series of adaptive instrumentation techniques. As part of the measurement operation, we will associate the measurements with a local call stack. The correlated local stack/performance measurement data will feed an analysis pipeline consisting of both node-local analysis methods, and distributed, wider-context analysis methods. The resulting data store will support a high-level query interface used by visualization and data analysis reporting tools informing the user. Such a system also enables dynamic tuning, and feedback-directed optimization.