Name
Abstract | ||
|---|---|---|
Software performance is critical for how users perceive the quality of software products. Performance bugs---programming errors that cause significant performance degradation---lead to poor user experience and low system throughput. Designing effective techniques to address performance bugs requires a deep understanding of how performance bugs are discovered, reported, and fixed. In this paper, we study how performance bugs are discovered, reported to developers, and fixed by developers, and compare the results with those for non-performance bugs. We study performance and non-performance bugs from three popular code bases: Eclipse JDT, Eclipse SWT, and Mozilla. First, we find little evidence that fixing performance bugs has a higher chance to introduce new functional bugs than fixing non-performance bugs, which implies that developers may not need to be overconcerned about fixing performance bugs. Second, although fixing performance bugs is about as error-prone as fixing nonperformance bugs, fixing performance bugs is more difficult than fixing non-performance bugs, indicating that developers need better tool support for fixing performance bugs and testing performance bug patches. Third, unlike many non-performance bugs, a large percentage of performance bugs are discovered through code reasoning, not through users observing the negative effects of the bugs (e.g., performance degradation) or through profiling. The result suggests that techniques to help developers reason about performance, better test oracles, and better profiling techniques are needed for discovering performance bugs.
|
Year | DOI | Venue |
|---|---|---|
2013 | 10.1109/MSR.2013.6624035 | MSR |
Keywords | Field | DocType |
performance bug,better tool support,better test oracle,performance degradation,eclipse jdt,significant performance degradation,testing performance bug patch,software performance,non-performance bug,developers reason,cognition,software quality,statistics,sociology,inspection,computer bugs | Software release life cycle,Software engineering,Computer science,Software bug,Regression testing,Software performance testing,Security bug,Bebugging,Software quality,Operating system,Database,Debugging | Conference |
Volume | ISBN | Citations |
2 | 978-1-4673-2936-1 | 43 |
PageRank | References | Authors |
1.27 | 33 | 3 |
Name | Order | Citations | PageRank |
|---|---|---|---|
| Adrian Nistor | 1 | 174 | 5.85 |
| Tian Jiang | 2 | 43 | 1.27 |
| Lin Tan | 3 | 1648 | 67.22 |