Performance Testing
summary
Performance testing focuses on concrete practices: using BenchmarkDotNet for isolated measurements, reporting ranges and quantiles instead of just means, and comparing distributions with a shift function to reveal where slowdowns occur. Practical rules appear: the vague “30-iteration” statistical rule of thumb, a common exploitable outlier example (3–4s typical runs versus occasional 26s spikes), and a published n log n change‑point algorithm plus a dashboard and adaptive alarm approach that already detects multimodality and compound regressions.
AI-written summary · about
chapters (6)
- 0:00Start
- 0:13Introduction
- 3:04Performance Summary Reports
- 12:23Performance Comparing Reports
- 37:06Performance Alarus & Asserts
- 45:15Conclusion
related talks
57mOpen Forum on Performance Testing
42mMeasuring Performance with Functional Tests: A Low-Effort Approach for High Impact
29mProgressive Testing to Meet the Performance Imperative
41mContinuous Performance Testing in DevOps
54mPerformance tests and other lies
28mPerformance is a Feature It Should Be Tested as Such
53mEarly Performance Testing: Finding News You Can Use
47mLee Barnes: Maximizing the Value of Performance Testing Throughout the Software Development Cycle