Eclipse Trace Compass: Execution Comparison!

The feature allows a user to run a program, trace it, patch it, trace it again and observe the differences.
This is a great feature that took years to bring to you. We are excited to show off the initial results.
This allows differential flame graphs to be shown comparing two executions. A flame graph is a visualization tool used to analyze performance and identify bottlenecks in software systems. It’s particularly useful for profiling CPU and memory usage in applications. A differential flame graph is a specialized form of flame graph used to compare two different states of an application’s performance. It highlights the differences in performance metrics, such as CPU time or memory usage, between two snapshots of an application's execution.
This enhancement was originally implemented as a proof of concept by Francois Doray (1). Then Fariba Daneshgar (2) and Maryam Ekslasi (3) made it able to handle generic callstacks. Vlad Arama finished off the product and stabilized it.
[1] ieeexplore.iee...
[2] www.dorsal.pol...
[3] www.dorsal.pol...

[@MarkRuvald]

DTW. Dynamic time warp. Would align automatically

[@EclipseTraceCompass]

We support DTW, in fact we have the first implementation of LIANA. www.sciencedirect.com/science/article/abs/pii/S1084804514001623
However, this would not help in the context of flame graphs, but flame charts. Here is a video describing the difference. ua-cam.com/video/ZrjuJKjAUns/v-deo.html . Basically a flame chart shows your callstack vs time, a flame graph is a weighted tree of function durations that are aggregated from a callstack over time.
Also, we find the naming (Flame Graph/Flame Chart) to be confusing. Callstack over time and flame graph would be clearer. However, we tried to align with industry standard nomenclature.
Thanks for the comment!

[@marcdumais]

Nice job Vlad!

[@EclipseTraceCompass]

Truly a great intern!