Really like Bjedov's presentation on performance testing, just recap her idea here one more time :)
1. Mentally: tell yourself Performance testing is not that hard!
2. The concept of performance testing—different people has different idea; benchmark should be paid close attention to, which includes a set of environment, a suite of test scenarios, a group of profiling point. All these can be adjusted according to the testing context/situation.
3. Google is more focusing on service-tire/back-end than web-tire/front-end, they think front-end performance issue can be found through functional testing. Yahoo is different, they more focus on front-end tuning, they developed many rules to follow
4. You can not do everything like functional testing, please follow 2/8 golden rule.
5. I'll run this benchmark with different loads against a loosely controlled system (it would be nice to have 100 machines all to myself for every service we have, which I can use once a day or once a week, but that would be expensive and unrealistic) and investigate its behavior. Which transactions are taking the most time? Which transactions seem to get progressively worse with increasing load? Which transactions seem unstable (I cannot explain their behavior)?
6. If you have questions, please ask dev, but notice do not believe them very easily J only thing you need do is do the benchmark testing again to verify it.
7. Create all kinds of diagram and results, discuss with dev, then take some suggestions from them, and refine our benchmark as the final one, keep daily tracking for performance trend. Avoid big surprise.
8. Do profiling in time and isolation testing. It will help you find the bottleneck deeper and more accurate.
9. Monitor your services during performance tests, monitor CPU, memory and I/O usage in minimum
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment