DOI: 10.5281/zenodo.818592
title: How Developers Locate Performance Bugs — Supplementary Material

description: <strong>Abstract:</strong>

<em>Background:</em> Performance bugs can lead to severe issues regarding computation efficiency, power consumption, and user experience. Locating these bugs is a difficult task because developers have to judge for every costly operation whether runtime is consumed necessarily or unnecessarily. Objective: We wanted to investigate how developers, when locating performance bugs, navigate through the code, understand the program, and communicate the detected issues.

<em>Method:</em> We performed a qualitative user study observing twelve developers trying to fix documented performance bugs in two open source projects. The developers worked with a profiling and analysis tool that visually depicts runtime information in a list representation and embedded into the source code view.

<em>Results:</em> We identified typical navigation strategies developers used for pinpointing the bug, for instance, following method calls based on runtime consumption. The integration of visualization and code helped developers to understand the bug. Sketches visualizing data structures and algorithms turned out to be valuable for externalizing and communicating the comprehension process for complex bugs.

<em>Conclusion:</em> Fixing a performance bug is a code comprehension and navigation problem. Flexible navigation features based on executed methods and a close integration of source code and performance information support the process.

<strong>Dataset:</strong>


	
	<strong>Tutorial:</strong> We provide the slides (PDF) and the video (MP4) we used in the tutorial phase of our study.
	
	
	<strong>Locating Bugs:</strong> We also provide supplementary material for each research question. We provide the advices we prepared for each bug in case a team got stuck (PDF); the questions we asked after each bug fixing session can be found on the introduction slides (PDF).

	
		
		<strong>RQ1:</strong> Navigating and Understanding

		
			
			<strong>RQ1.1:</strong> <em>How was information from the profiling tool or other parts of the IDE used to locate the performance bug?</em> Cross-case analysis (in German) (XLSX+ODS)
			
			
			<strong>RQ1.2:</strong> <em>Is the in-situ visualization of the profiling data beneficial compared to a traditional list representation?</em> Cross-case analysis (in German) (XLSX+ODS)
			
			
			<strong>RQ1.3:</strong> <em>What navigation strategies do developers pursue to locate a specific performance bug?</em> Interaction logs (TXT), Navigation visualizations (SVG), Screen recordings for Bug 3 (MP4, without audio because of confidentiality)
			
		
		
		
		<strong>RQ2:</strong> Understanding and Communicating

		
			
			<strong>RQ2.1:</strong> <em>How do developers communicate with each other when locating a performance bug?</em> Coding (XLSX+ODS), Sketches (PDF), Screen recordings for Bug 3 (MP4, without audio because of confidentiality)
			
			
			<strong>RQ2.2:</strong> <em>Could sketches help to understand and communicate a performance bug?</em> Coding (XLSX+ODS), Sketches (PDF), Cross-case analysis (in German) (XLSX+ODS), Sketching videos for Bug 3 (MP4, without audio because of confidentiality)
			
		
		
	
	
	
	<strong>Questionnaire:</strong> The questionnaire that the participants filled out at the end of the study can be found here (PDF).
description: {"references": ["Baltes et al. \u2014 Navigate, Understand, Communicate: How Developers Locate Performance Bugs (ESEM 2015): http://ieeexplore.ieee.org/document/7321208/", "Baltes et al. \u2014 Navigate, Understand, Communicate: How Developers Locate Performance Bugs (ESEM 2015): https://sbaltes.github.io/assets/pdf/esem15-debugging.pdf"]}