Browsing by Autor "Fabian Beck"

Now showing 1 - 5 of 5

Enhancing Commit Graphs with Visual Runtime Clues
(2019) Juan Pablo Sandoval Alcocer; Harold Camacho Jaimes; Diego Elias Costa; Alexandre Bergel; Fabian Beck
Monitoring software performance evolution is a daunting and challenging task. This paper proposes a lightweight visualization technique that contrasts source code variation with the memory consumption and execution time of a particular benchmark. The visualization fully integrates with the commit graph as common in many software repository managers. We illustrate the usefulness of our approach with two application examples. We expect our technique to be beneficial for practitioners who wish to easily review the impact of source code commits on software performance.
Performance Evolution Matrix: Visualizing Performance Variations Along Software Versions
(2019) Juan Pablo Sandoval Alcocer; Fabian Beck; Alexandre Bergel
Software performance may be significantly affected by source code modifications. Understanding the effect of these changes along different software versions is a challenging and necessary activity to debug performance failures. It is not sufficiently supported by existing profiling tools and visualization approaches. Practitioners would need to manually compare calling context trees and call graphs. We aim at better supporting the comparison of benchmark executions along multiple software versions. We propose Performance Evolution Matrix, an interactive visualization technique that contrasts runtime metrics to source code changes. It combines a comparison of time series data and execution graphs in a matrix layout, showing performance and source code metrics at different levels of granularity. The approach guides practitioners from the high-level identification of a performance regression to the changes that might have caused the issue. We conducted a controlled experiment with 12 participants to provide empirical evidence of the viability of our method. The results indicate that our approach can reduce the effort for identifying sources of performance regressions compared to traditional profiling visualizations.
Performance Evolution Matrix: Visualizing Performance Variations along Software Versions
(Figshare (United Kingdom), 2019) Juan Pablo Sandoval Alcocer; Fabian Beck; Alexandre Bergel
# Performance Evolution Matrix This repository contains the artifacts needed to replicate our experiment in the paper "Performance Evolution Matrix". # Video Demo [download](https://github.com/jpsandoval/PerfEvoMatrix/blob/master/MatrixMovie.mp4) # XMLSupport and GraphET Examples To open the XMLSupport and GraphET Examples (which appears in the paper) execute the following commands in a Terminal. **MacOSX.** We do all the experiments in a Mac Book Pro. To open the Matrix execute the following command in the folder where this project was downloaded. ``` ./Pharo-OSX/Pharo.app/Contents/MacOS/Pharo Matrix.image ``` **Windows.** You may also run the experiment in Windows, but depending on the windows version you have installed it may be some some UI bugs. ``` cd Pharo-Windows Pharo.exe ../XMLSupportExample.image ``` **Open the Visualization.** Please select the following code, then execute it using the green play button (at the top right of the window). ``` ToadBuilder xmlSupportExample. ``` or ``` ToadBuilder graphETExample. ``` **Note.** There are two buttons at the panel top left In (zoom in) and Out (zoom out). To move the visualization just drag the moves over the panel. # Experiment This subsection describe how to execute the tools, for replicating our experiment. ## Baseline The baseline contains the tools and the project-dataset to realize the tasks described in the paper (identifying and understanding performance variations). ## Open the Baseline **MacOSX.** We do all the experiments in a Mac Book Pro. To open the Baseline execute the following command in the folder where this project was downloaded. ``` ./Pharo-OSX/Pharo.app/Contents/MacOS/Pharo Baseline.image ``` **Windows.** You may also run the experiment in Windows, but depending on the windows version you have installed it may be some some UI bugs. ``` cd Pharo-Windows Pharo.exe ../Baseline.image ``` ## Open a Project There are three projects under study, depending on the project you wanna use for the task, you may execute one of the following scripts. For executing a script press Cmd-d or right-click and press do it. **Roassal** ``` TProfileVersion openRoassal. ``` **XML** ``` TProfileVersion openXML. ``` **Grapher** ``` TProfileVersion openGrapher. ``` ## Baseline Options For each project, we provide a UI which contains all the tools we use as a baseline. Each item in the list is a version of the selected project. <img src="images/baseline.png" width="300"> - Browse: open a standard window to inspect the code of the project in the selected version. - Profile: open a window with a call context tree for the selected version. - Source Diff: open a window with the code differences between the selected version and the previous one. - Execution Diff: open a window with the merge call context tree gathered from the selected version and the previous one. **Note.** All these options require you select first a item in the list. # Matrix ## Open Matrix Image. **MacOSX.** We do all the experiments in a Mac Book Pro. To open the Matrix execute the following command in the folder where this project was downloaded. ``` ./Pharo-OSX/Pharo.app/Contents/MacOS/Pharo Matrix.image ``` **Windows.** You may also run the experiment in Windows, but depending on the windows version you have installed it may be some some UI bugs. ``` cd Pharo-Windows Pharo.exe ../Matrix.image ``` ## Open a project There are three projects under study, depending on the project you wanna use for the task, you may execute one of the following scripts. For executing a script press Cmd-d or right-click and press do it. **Roassal** ``` ToadBuilder roassal. ``` **XML** ``` ToadBuilder xml. ``` **Grapher** ``` ToadBuilder grapher. ``` # Data Gathering Before each participant starts a task we execute the following script in Smalltalk. For executing a script press Cmd-d or right-click and press do it. It allows us to track the time that a user starts the experiment and how many mouse clicks, movements. ``` UProfiler newSession. UProfiler current start. ``` After finishing the task we executed the following script. It stop recording the mouse events and save the stops time. ``` UProfiler current end. ``` The last script generates a file with the following information: start time, end time, number of clicks, number of mouse movements, and the number of mouse drags (we do not use this last one). ``` 11:34:52.5205 am,11:34:56.38016 am,14,75,0 ``` # Quit To close the artifact, just close the window or press click in any free space of the window and select quit.
Performance Evolution Matrix: Visualizing Performance Variations along Software Versions
(European Organization for Nuclear Research, 2019) Juan Pablo Sandoval Alcocer; Fabian Beck; Alexandre Bergel
# Performance Evolution Matrix This repository contains the artifacts needed to replicate our experiment in the paper "Performance Evolution Matrix". # Video Demo [download](https://github.com/jpsandoval/PerfEvoMatrix/blob/master/MatrixMovie.mp4) # XMLSupport and GraphET Examples To open the XMLSupport and GraphET Examples (which appears in the paper) execute the following commands in a Terminal. **MacOSX.** We do all the experiments in a Mac Book Pro. To open the Matrix execute the following command in the folder where this project was downloaded. ``` ./Pharo-OSX/Pharo.app/Contents/MacOS/Pharo Matrix.image ``` **Windows.** You may also run the experiment in Windows, but depending on the windows version you have installed it may be some some UI bugs. ``` cd Pharo-Windows Pharo.exe ../XMLSupportExample.image ``` **Open the Visualization.** Please select the following code, then execute it using the green play button (at the top right of the window). ``` ToadBuilder xmlSupportExample. ``` or ``` ToadBuilder graphETExample. ``` **Note.** There are two buttons at the panel top left In (zoom in) and Out (zoom out). To move the visualization just drag the moves over the panel. # Experiment This subsection describe how to execute the tools, for replicating our experiment. ## Baseline The baseline contains the tools and the project-dataset to realize the tasks described in the paper (identifying and understanding performance variations). ## Open the Baseline **MacOSX.** We do all the experiments in a Mac Book Pro. To open the Baseline execute the following command in the folder where this project was downloaded. ``` ./Pharo-OSX/Pharo.app/Contents/MacOS/Pharo Baseline.image ``` **Windows.** You may also run the experiment in Windows, but depending on the windows version you have installed it may be some some UI bugs. ``` cd Pharo-Windows Pharo.exe ../Baseline.image ``` ## Open a Project There are three projects under study, depending on the project you wanna use for the task, you may execute one of the following scripts. For executing a script press Cmd-d or right-click and press do it. **Roassal** ``` TProfileVersion openRoassal. ``` **XML** ``` TProfileVersion openXML. ``` **Grapher** ``` TProfileVersion openGrapher. ``` ## Baseline Options For each project, we provide a UI which contains all the tools we use as a baseline. Each item in the list is a version of the selected project. <img src="images/baseline.png" width="300"> - Browse: open a standard window to inspect the code of the project in the selected version. - Profile: open a window with a call context tree for the selected version. - Source Diff: open a window with the code differences between the selected version and the previous one. - Execution Diff: open a window with the merge call context tree gathered from the selected version and the previous one. **Note.** All these options require you select first a item in the list. # Matrix ## Open Matrix Image. **MacOSX.** We do all the experiments in a Mac Book Pro. To open the Matrix execute the following command in the folder where this project was downloaded. ``` ./Pharo-OSX/Pharo.app/Contents/MacOS/Pharo Matrix.image ``` **Windows.** You may also run the experiment in Windows, but depending on the windows version you have installed it may be some some UI bugs. ``` cd Pharo-Windows Pharo.exe ../Matrix.image ``` ## Open a project There are three projects under study, depending on the project you wanna use for the task, you may execute one of the following scripts. For executing a script press Cmd-d or right-click and press do it. **Roassal** ``` ToadBuilder roassal. ``` **XML** ``` ToadBuilder xml. ``` **Grapher** ``` ToadBuilder grapher. ``` # Data Gathering Before each participant starts a task we execute the following script in Smalltalk. For executing a script press Cmd-d or right-click and press do it. It allows us to track the time that a user starts the experiment and how many mouse clicks, movements. ``` UProfiler newSession. UProfiler current start. ``` After finishing the task we executed the following script. It stop recording the mouse events and save the stops time. ``` UProfiler current end. ``` The last script generates a file with the following information: start time, end time, number of clicks, number of mouse movements, and the number of mouse drags (we do not use this last one). ``` 11:34:52.5205 am,11:34:56.38016 am,14,75,0 ``` # Quit To close the artifact, just close the window or press click in any free space of the window and select quit.
Visually Exploring Object Mutation
(2016) Rodrigo Schulz; Fabian Beck; Jhonny Wilder Cerezo Felipez; Alexandre Bergel
Object-oriented programming supports object mutation during a program execution. A mutation occurs whenever a value is assigned to an object field. Analyzing the evolution of object mutation is known to be difficult. Unfortunately, classical code debuggers painfully support the analysis of object mutations. Object Evolution Blueprint is a visualization dedicated to exploring object mutation over time. Our blueprint visually and concisely represents sequences of field mutations. The history of each field is adequately shown with respect to the dynamic value types. We have observed the use of our blueprint with three practitioners. Our visualization has been well received and accepted to complete two different software comprehension tasks. Moreover, our user study shows that the visualization is both intuitive and simple to learn.