Tracing of Multi-Threaded Java Applications in Score-P Using Bytecode Instrumentation

Conference: ARCS Workshop 2018 - 31th International Conference on Architecture of Computing Systems
04/09/2018 - 04/12/2018 at Braunschweig, Germany

Proceedings: ARCS 2018

Pages: 8Language: englishTyp: PDF

Personal VDE Members are entitled to a 10% discount on this title

Authors:
Frenzel, Jan; Feldhoff, Kim; Jaekel, Rene; Mueller-Pfefferkorn, Ralph (Center for Information Services and High Performance Computing (ZIH), Technische Universit├Ąt Dresden, 01062 Dresden, Germany)

Abstract:
Thread-parallel Java applications received a substantial boost in the research field of High Performance Computing over the past years. In order to efficiently execute multithreaded Java applications, an analysis of their performance is indispensable. This requires a scalable runtime performance measurement infrastructure due to the high number of used threads. The established, open-source tracing framework Score-P provides such an infrastructure. However, it only provides basic support for multi-threaded Java applications so far. In this paper, we present a more sophisticated instrumentation approach based on Java bytecode transformations and implement the approach in Score-P. The approach allows to trace an application without requiring users to modify their source code. In contrast to instrumentation approaches based on the Java Virtual Machine Tool Interface JVMTI, it does not need filter checking and thus, has a comparable low run-time overhead. However, if needed, function and thread related events of the application can be filtered at runtime. Additionally, class files can be selected such that only those classes of an application are recorded, which users are interested in. We apply the proposed instrumentation approach to the LU kernel of the established Java benchmark suite SPECjvm2008 at a modern HPC shared-memory machine and show the quality of the implementation by determining the tracing overheads of the instrumented versions for different test scenarios using varying numbers of Java threads.