“8 Performance testing tips that every Test Engineer should know.”
summary
Defines eight concrete checks: measure CPU cores not just utilization, inspect RAM vs swap and JVM stack vs heap behaviour (stack overflow vs heap OOM) and watch garbage collection impact, target API response under 200 ms, design for millions of transactions/sec by measuring throughput and DB read/write timings, simulate distributed load across servers, tolerate ≤1% error under stress, and pair real‑time APM with synthetic checks (e.g. Selenium) to catch regressions.
AI-written summary · about
related talks
54mPerformance tests and other lies
57mOpen Forum on Performance Testing
53mEarly Performance Testing: Finding News You Can Use
29mProgressive Testing to Meet the Performance Imperative
41mMartijn Goossens: Become a Performance Test Master - the Non-Technical Side of Things
08mCommon Mistakes in Performance testing
38mPerformance 101
47mPractical Performance Analysis