Last- und Performancetests in der Cloud?!
summary
Claims that matter: cloud vendors scale resources not applications and that testing reveals where that breaks. Concrete methods and results: load, stress, spike, soak and configuration testing with measurable thresholds (example: one server ≈250 req/s, long runs of billions of requests, network tests from megabits to double‑digit gigabits). Tools and stacks actually used: stormforger platform, Tsung and JMeter for drives, AWS examples (auto‑scaling, DynamoDB/Lambda) and tests showing whether changes and auto‑scale policies actually work.
AI-written summary · about
chapters (21)
- 0:00Introduction
- 8:56The Cloud
- 9:46Why is this relevant
- 15:30Test methods
- 16:45Low testing
- 18:57Stress tests
- 20:53Scalability tests
- 23:12Spike testing
- 25:00Soak testing
- 27:18Configuration testing
- 28:12Configuration examples
- 31:13Performance pitfalls
- 32:47Resilience testing
- 35:30Is this any difference
- 36:32Test environments
- 41:31Recap
- 42:25Cycle
- 45:56Traffic spikes
- 48:52Summary
- 53:16Order of testing
- 55:10Testing tools
related talks
01h 08mPerformance testing in the cloud
12mExponential Load Testing...
09mPerformance is the first UX challenge to consider
40mPerformance Testing and Big Data
16m"Performance Testing: ..."
06mLightning Talk: Performance Engineering and Testing of Apps and Services Deployed on Cloud Foundry
33mPerformance Testing in Agile and DevOps
31mPerformance Engineering and Testing of Apps and Services Deployed on Cloudfoundry