Please use this identifier to cite or link to this item:
Scopus Web of Science® Altmetric
Type: Conference paper
Title: Automating the performance deviation analysis for multiple system releases: an evolutionary study
Author: Pinto, F.
Kulesza, U.
Treude, C.
Citation: Proceedings of the 15th International Working Conference on Source Code Analysis and Manipulation, 2015 / Godfrey, M., Lo, D., Khomh, F. (ed./s), pp.201-210
Publisher: IEEE
Issue Date: 2015
Series/Report no.: IEEE International Working Conference on Source Code Analysis and Manipulation
ISBN: 9781467375290
ISSN: 1942-5430
Conference Name: 15th IEEE International Working Conference on Source Code Analysis and Manipulation (SCAM) (27 Sep 2015 - 28 Sep 2015 : Bremen, Germany)
Editor: Godfrey, M.
Lo, D.
Khomh, F.
Statement of
Felipe Pinto, Uirá Kulesza, Christoph Treude
Abstract: This paper presents a scenario-based approach for the evaluation of the quality attribute of performance, measured in terms of execution time (response time). The approach is implemented by a framework that uses dynamic analysis and repository mining techniques to provide an automated way for revealing potential sources of performance degradation of scenarios between releases of a software system. The approach defines four phases: (i) preparation – choosing the scenarios and preparing the target releases; (ii) dynamic analysis – determining the performance of scenarios and methods by calculating their execution time; (iii) degradation analysis – processing and comparing the results of the dynamic analysis for different releases; and (iv) repository mining – identifying development issues and commits associated with performance deviation. The paper also describes an evolutionary study of applying the approach to multiple releases of the Netty, Wicket and Jetty frameworks. The study analyzed seven releases of each system and addressed a total of 57 scenarios. Overall, we have found 14 scenarios with significant performance deviation for Netty, 13 for Wicket, and 9 for Jetty, almost all of which could be attributed to a source code change. We also discuss feedback obtained from eight developers of Netty, Wicket and Jetty as result of a questionnaire.
Rights: © 2015 IEEE
DOI: 10.1109/SCAM.2015.7335416
Published version:
Appears in Collections:Aurora harvest 8
Computer Science publications

Files in This Item:
There are no files associated with this item.

Items in DSpace are protected by copyright, with all rights reserved, unless otherwise indicated.