Trace management and analysis with FrameSoC

Journées Mescal

Autrans, 18/03/2014

Generoso Pagano

generoso.pagano@inria.fr

Application tracing

2

• Powerful instrument to analyze application behavior

– Embedded Systems, Parallel computing, HPC, …

• Limited intrusivity

• Help debugging and profiling

ISSUES

• Different formats

• Different analysis

• Data volume

• Visualization scalability

FrameSoC: trace analysis infrastructure

3

• FrameSoC is developed within the SoC-Trace project

– INRIA, UJF, STMicroelectronics, ProbaYes, Magillem

• To tackle the above issues we propose FrameSoC

Data-accesssoftware library

Generic trace storage

Graphical environment for analysis

4

Data-accesssoftware library

Generic trace storage

Graphical environment for analysis

Many formats, many tools

5

tools

traces

Many formats, many tools

6

FrameSoC Trace DB

Generic Data-Model

tools

traces

Generic data-modeltools

traces

• Represent different trace formats– Self defining approach– Event categories

• Store various trace metadata• Store trace analysis results

FrameSoC

Analysis workflow

7

1

2filtering

statistics?

filter result

Analysis workflow

8

1

2

1 2

FrameSoC Trace DB

Generic Data-Model

Store analysis results

FrameSoC

• Tool cooperation

• Avoid long recomputations

trace data statistics

filtering

statistics?

Data-accesssoftware library

Generic trace storage

Graphical environment for analysis

SoC-Trace Library

• It is a set of Eclipse plugins

• Read/Write access to data abstracts storage details

– We read and write Java objects

• Factorization of trace-access functionalities

– Basic bricks to build analysis tools (e.g. Ocelotl)

10

Data-accesssoftware library

Generic trace storage

Graphical environment for analysis

FrameSoC Workbench

12

13

Data-accesssoftware library

Generic trace storage

Graphical environment for analysis

Let’s see FrameSoC in action!

An example: comparison of two traces

14

• Use case provided by Luka

native simgrid

15

native simgrid#

of

even

ts

time time

# o

f ev

ents

24 s

16

native simgrid#

of

even

ts

time time

# o

f ev

ents

24 s

17

native

18

native native

19

native native

simgrid

• Actual problem: simgrid assumed infinite GPU memory

• no swapping to the RAM occurred during simulation

Conclusion…

20

FrameSoC can facilitate trace analysis

Base analysis tools

Fast analysis

Hints to find the problem

Type/Producer filtering in Pie and HistogramTime filtering in PieProvide more statistical viewsImprove ergonomics…

First open-source release of FrameSoC in June 2014

…and Perspectives

21

Questions?