Common Mistakes in Performance testing
summary
Lists five concrete failure modes and fixes: missing realistic delays between actions so scripts run sequentially instead of using JMeter timers, wrong load model instead of ramp and steady or spikes, reused or small datasets and a blank/staging DB that hide slow queries, and no infrastructure monitoring so CPU goes from 90% to 200% while errors jump 5% → 30%. Recommends random data, distributed injectors, real geo placement and metrics tools like AppDynamics/New Relic.
AI-written summary · about
chapters (6)
- 0:00Introduction
- 0:40Inadequate user think time
- 2:55Inaccurate workload mode
- 4:59Improper infrastructure monitoring
- 6:08Inappropriate data
- 7:03Blank database
related talks
54mPerformance tests and other lies
31mHow we can manage performance testing?
41mMartijn Goossens: Become a Performance Test Master - the Non-Technical Side of Things
53mEarly Performance Testing: Finding News You Can Use
57mOpen Forum on Performance Testing
08m“8 Performance testing tips that every Test Engineer should know.”
14m3 Automation Testing Mistakes & How to Correct Them?
44mPerformance Testing: the way to make a true load