Martijn Goossens: Become a Performance Test Master - the Non-Technical Side of Things
summary
Practical recipe: run a one-hour test with ramp up for half the period, warm the environment first, test from the user locale, and include HTML/API, JS and media calls. Use JMeter, BlazeMeter, Gatling, Locust or NeoLoad. Aim for baseline response times around 400–1000 ms per request, zero error rate, and measure hits/sec and error spikes. Try stress/load/soak/spike tests; a found third‑party API was the real bottleneck and required scaling before production.
AI-written summary · about
chapters (9)
- 0:00Performance testing skills
- 1:27Why performance testing matters
- 3:53Types of performance tests
- 9:13Backend performance fundamentals
- 14:34Setting up a performance test
- 19:52Running test and metrics
- 27:18Analyzing test results
- 35:51Key takeaways
- 38:40Q&A
related talks
26mLoad testing websites following the steps of a user journey
57mOpen Forum on Performance Testing
01h 10mPerformance Testing Crash Course
31mHow we can manage performance testing?
50mHow to Think like a Performance Engineer
26mIntroduction to Load Testing
53mEarly Performance Testing: Finding News You Can Use
28mStress Testing in Production: The New York Times Engineering Survival Guide