Open Forum on Performance Testing
summary
Defines performance testing as checking efficiency beyond simple load tests and distinguishes synthetic scripts from organic traffic. Uses Chrome DevTools for front-end timings, APM agents for backend traces, and JMeter for load generation, illustrates a case where large servers failed under just five concurrent users, and discusses risk-driven scenarios (e.g., Ticketmaster peak sales), mobile vs server metrics (CPU, RAM, bandwidth), ethics of saturating production, and recommends learning HTTP/API automation, frontend rendering, and SQL tuning.
AI-written summary · about
chapters (15)
- 0:00Welcome
- 2:12Performance testing definition
- 6:31Load vs performance testing
- 8:17Starting performance testing
- 12:52Success metrics
- 17:35Performance roles
- 24:35Ethics in load testing
- 29:52Common performance errors
- 34:12Favorite performance tools
- 37:45Mobile app performance testing
- 43:04Costs by architecture
- 44:29Alternatives to traditional tools
- 46:34Performance testing checklist
- 51:50Tool selection
- 55:28Additional resources
related talks
44mPerformance Testing: the way to make a true load
29mProgressive Testing to Meet the Performance Imperative
40mAutomated Performance Testing In Preproduction
41mMartijn Goossens: Become a Performance Test Master - the Non-Technical Side of Things
41mContinuous Performance Testing in DevOps
53mEarly Performance Testing: Finding News You Can Use
44mContinuous Performance Testing in DevOps
01h 10mPerformance Testing Crash Course