Last-Minute Performance Testing
summary
A rushed two-week performance test aimed to validate a learning platform at 20,000 users but uncovered problems with non-HTTP chat protocols (XMPP/BOSH/WebSocket), missing features in the load tool, and an environment that drops traffic. The team modified the Erlang load tester Tsung to add cookie support, confirmed behavior with packet captures, and observed tests fail after about 13 minutes when Cloudflare flagged the simulated traffic as an attack; a working Tsung patch exists, but the system could not survive real load, prompting the client to pursue architecture changes.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 3:25Load testing plan issues
- 7:23Project and XMPP protocol
- 12:29Tool selection first tests
- 15:48Cookies problems
- 20:19Tool modification developer work
- 24:17CloudFlare detection issues
- 28:24Results analysis
- 30:47Q&A
- 35:50Key takeaways
related talks
16mPerformance testing – under pressure!
45mBeat the rush! Designing effective load tests for your web application
44mOnce upon a load test in real time
57mLast- und Performancetests in der Cloud?!
57mOpen Forum on Performance Testing
48mHow to not Crash in Prod, Load Testing Crash Course
01h 10mPerformance Testing Crash Course
41mMartijn Goossens: Become a Performance Test Master - the Non-Technical Side of Things