Companion of the 2018 ACM/SPEC International Conference on Performance Engineering 2018
DOI: 10.1145/3185768.3186404
|View full text |Cite
|
Sign up to set email alerts
|

How to Detect Performance Changes in Software History

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
2
1

Citation Types

0
5
0

Year Published

2019
2019
2023
2023

Publication Types

Select...
2
2
1

Relationship

0
5

Authors

Journals

citations
Cited by 9 publications
(5 citation statements)
references
References 21 publications
0
5
0
Order By: Relevance
“…To mitigate this threat, we have compared 30 executions of each test case on the original program and each mutant.Additionally, we have performed a statistical analysis of the execution times and we have used three different thresholds (p-values). More complex methods could be used, like the ones proposed by Reichelt and Kühne [9]. However, the methods that require many executions would make the application of the technique excessively expensive.…”
Section: Construct Validitymentioning
confidence: 99%
See 1 more Smart Citation
“…To mitigate this threat, we have compared 30 executions of each test case on the original program and each mutant.Additionally, we have performed a statistical analysis of the execution times and we have used three different thresholds (p-values). More complex methods could be used, like the ones proposed by Reichelt and Kühne [9]. However, the methods that require many executions would make the application of the technique excessively expensive.…”
Section: Construct Validitymentioning
confidence: 99%
“…In contrast to functional bugs, performance bugs do not usually produce wrong results or crashes in the program under test, and therefore, they cannot be detected by simply inspecting the program output. Furthermore, performance indicators are by nature non-deterministic and can vary among executions due to numerous factors, such as the device hardware, configuration settings or the current workload [9]. For example, suppose a mobile shopping app that consumes 30 Mb of memory: Is this the expected performance?…”
Section: Introductionmentioning
confidence: 99%
“…Some approaches to enhance performance testing include the use of static code analysis to discover performance errors. The authors of [18] determine a test plan based on code commits and the use of artificial unit tests to compare the performance between different versions. Meanwhile, the work presented on [17] describes the performance analysis of software systems as a comparison of two versions of software and their performance results to find possible (regression) bugs.…”
Section: Background and Related Workmentioning
confidence: 99%
“…Other performance testing approaches are based on static code analysis. For instance, the authors of [34] determine the performance tests based on commits and the usage of unittests. Meanwhile, the work presented in [33] describes the performance analysis of software systems as a comparison of two versions of software and their performance results to find possible (regression) bugs.…”
Section: Background and Related Workmentioning
confidence: 99%
“…Conducting performance testing typically requires a lot of effort and expertise from testers. The performance of each application is unique and although the application could be the same, different versions and releases are still distinctive, so the set of performance tests needs to be updated accordingly [34]. This problem emphasizes the need for an expert on the application under test in order to get some insights regarding its weakness [38].…”
Section: Introductionmentioning
confidence: 99%