An open-source tool-chain for performance analysis

Kevin Coulomb, Augustin Degomme, Mathieu Faverge, François Trahay

Research output: Chapter in Book/Report/Conference proceedingConference contributionpeer-review

Abstract

Modern supercomputers with multi-core nodes enhanced by accelerators as well as hybrid programming models introduce more complexity in modern applications. Efficiently exploiting all of the available resources requires a complex performance analysis of applications in order to detect time-consuming or idle sections. This paper presents an open-source tool-chain for analyzing the performance of parallel applications. It is composed of a trace generation framework called EZTRACE, a generic interface for writing traces in multipe formats called GTG, and a trace visualizer called VITE. These tools cover the main steps of performance analysis - from the instrumentation of applications to the trace analysis - and are designed to maximize the compatibility with other performance analysis tools. Thus, these tools support multiple file formats and are not bound to a particular programming model. The evaluation of these tools show that they provide similar performance compared to other analysis tools.

Original languageEnglish
Title of host publicationProceedings of the 5th International Workshop on Parallel Tools for High Performance Computing 2011
Pages37-48
Number of pages12
DOIs
Publication statusPublished - 1 Dec 2012
Externally publishedYes
Event5th International Workshop on Parallel Tools for High Performance Computing, HPC 2011 - Dresden, Germany
Duration: 26 Sept 201127 Sept 2011

Publication series

NameProceedings of the 5th International Workshop on Parallel Tools for High Performance Computing 2011

Conference

Conference5th International Workshop on Parallel Tools for High Performance Computing, HPC 2011
Country/TerritoryGermany
CityDresden
Period26/09/1127/09/11

Fingerprint

Dive into the research topics of 'An open-source tool-chain for performance analysis'. Together they form a unique fingerprint.

Cite this