Performance 101
summary
Claims performance is a business metric, not just speed, and gives a concrete checklist: establish a baseline and acceptance criteria, measure availability, response time, channel capacity, latency, throughput, and run targeted tests (isolation, load, stress, soak, spike, breakpoint, configuration, internet). Recommends practical tactics like segregating production servers for stress tests, using tools such as Catchpoint for distributed checks, and a methodology: identify environment, design tests, run, analyze, tune, retest. Watch if actionable measurement and testing steps matter.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 0:53Agenda
- 2:18What to measure
- 13:23Methodology
- 14:03Testing Types
- 19:26Configuration Testing
- 20:23Internet Testing
- 22:31Performance Hides
- 28:23Stress Testing
- 30:31Measurement
- 31:05Test Environment
- 32:08Business Use Case
- 33:46Service Providers
- 34:29Resource Exhaustion
- 35:57Team Response Time
- 36:23Time to Market
related talks
12mPerformance In Context
01h 00mPerformance In Modern Times: An Evolutionary Journey
45mPerformance testing from scratch
29mProgressive Testing to Meet the Performance Imperative
41mPerformance Engineering in the Age of DevOps and Agile
28mPerformance is a Feature It Should Be Tested as Such
47mPractical Performance Analysis
09mPerformance is the first UX challenge to consider