Backend
Evaluating Change Point Detection Methods for Software Performance Regression Analysis
arXiv cs.SE0 views
arXiv:2610.09023v1 Announce Type: new Abstract: Performance issues in software systems are a critical quality issue that can erode user trust, violate service-level agreements, and ultimately affect business efficiency. Consequently, software performance engineering has shifted its focus to developing robust techniques to detect performance regressions as early as possible in the development cycle. Performance regression analysis often relies on time series of performance measurements to detect significant changes in performance behavior. Change Point Detection (CPD) methods have been widely used to automate the identification of such changes in various domains, including finance, healthcare, and performance monitoring. However, the effectiveness of these methods for software performance measurements has not been thoroughly evaluated. In this paper, we present a comprehensive study to evaluate the effectiveness of various CPD methods on real-world software performance measurement datasets. We start by collecting performance measurement data from three large software systems and characterizing the unique properties of performance time series data. Then, we undertake a large-scale effort to annotate and evaluate the consistency of human annotators' identification of potential performance changes. Thereafter, we evaluate the accuracy of twelve distinct CPD methods in detecting potential performance changes, providing insights into their applicability and effectiveness in software performance regression analysis.
Source:https://arxiv.org/abs/2610.09023PreviousPsychological Safety in Software Engineering Teams: A Systematic Mapping Study of Team Processes and PerformanceNextLarge-scale Repository Engineering via Agent-Native Reusable Code Primitives
Related posts
I read all 308 open jobs at xAI: 54% are in its data center team, and most of them are in Memphis
0dev.to AI
Claude Code marketing analytics with an app-scoped key
0dev.to AI
I red-teamed my own support bot with 30 scenarios. It failed 7 — here's the harness.
0dev.to AI
The Log That Told Everyone the Password: Redacting Secrets in n8n Execution Logs
0dev.to WebDev
Your AI Portal Isn't Ready Until a Stranger Can Recover from Failure
0dev.to WebDev
API traffic monitoring: what to track, and how to set it up for a Node API
0dev.to Security