Is Source-code Isolation Viable for Performance Characterization? - Archive ouverte HAL Access content directly
Conference Papers Year : 2013

Is Source-code Isolation Viable for Performance Characterization?

(1) , (1) , (1, 2) , (1, 2)
1
2

Abstract

Source-code isolation finds and extracts the hotspots of an application as independent isolated fragments of code, called codelets. Codelets can be modified, compiled, run, and measured independently from the original application. Source-code isolation reduces benchmarking cost and allows piece-wise optimization of an application. Source-code isolation is faster than whole-program benchmarking and optimization since the user can concentrate only on the bottlenecks. This paper examines the viability of using isolated codelets in place of the original application for performance characterization and optimization. On the NAS benchmarks, we show that codelets capture 92.3% of the original execution time. We present a set of techniques for keeping codelets as faithful as possible to the original hotspots: 63.6% of the codelets have the same assembly as the original hotspots and 81.6% of the codelets have the same run time performance as the original hotspots.
Not file

Dates and versions

hal-00952290 , version 1 (26-02-2014)

Identifiers

Cite

Chadi Akel, Yuriy Kashnikov, Pablo de Oliveira Castro, William Jalby. Is Source-code Isolation Viable for Performance Characterization?. International Workshop on Parallel Software Tools and Tool Infrastructures (PSTI), Oct 2013, Lyon, France. pp.977 - 984, ⟨10.1109/ICPP.2013.116⟩. ⟨hal-00952290⟩

Collections

CNRS UVSQ
85 View
0 Download

Altmetric

Share

Gmail Facebook Twitter LinkedIn More