Performance testing – under pressure!
summary
A mobile streaming service on Amazon Cloud faces a proprietary binary protocol and SSL decryption limits so performance testing uses NeoLoad to JMeter conversion, captures REST traffic via a proxy, and simulates 250-user simulation because 40,000 users is unaffordable. Tests surface broken muffin libraries and JDK issues, show backend scaling limits, and lead to embedding a JMeter SDK for internal load runs and knowledge transfer so the system stabilizes before wider rollout.
AI-written summary · about
chapters (4)
- 0:00Performance testing intro
- 3:53Mobile streaming cloud project
- 13:45Lessons from young company
- 15:44Summary & Q&A
related talks
39mLast-Minute Performance Testing
01h 08mPerformance testing in the cloud
41mMartijn Goossens: Become a Performance Test Master - the Non-Technical Side of Things
43mThe Perf Testing Trifecta for Optimal End User Experience
57mOpen Forum on Performance Testing
33mHow much pressure can your app handle - Performance testing with Ruby
31mPerformance Engineering and Testing of Apps and Services Deployed on Cloudfoundry
01h 32mUsing JMeter to perform Load-Testing on PowerServer's Web API
