This is a free tool from Microsoft. I personally think it is "very easy" to use. At least it can be downloaded from Microsoft's official website without looking for a variety of registration machines or activation codes.
For more information and usage, see:
Http://www.cnblogs.com/suchenge/articles/884129.html
Http://www.williamlong.info/info/archives/196.html
The author wrote clearly and well. Here I will record some of my usage experiences.
The reason why I want to use was is to test the performance of a small module written by myself. The module itself is small, but for various reasons, I am not at ease. Then, I downloaded was, installation and use.
Some of the problems I encountered during the learning process are as follows:
- About the get parameter random: I thought he would generate his own parameter results. I always showed signs that "the application didn't get the parameter" in the test. Finally, after various attempts, I finally understood, this "random number" is random within the range you specified. OK, I wrote a small consoleProgramWrite the number of 1000 rows (actually 999 rows of ^_^) in a text file and copy and paste it in. Okay, well, my application finally received the random number.
- Bugs found during the test: Stress testing is really useful. I have written a good program and there is almost no problem in manual testing. Only a few lines are found during testing.CodeThere are obvious performance problems ...... Finally, it was changed. (In fact, there is still a problem. I can't solve it, but I just reduced it ......);
- Stress Level and stress Multiplier: I didn't tell the two things at last, but something interesting happened in the test. First I set both to 1 and then adjust the number of users (from 1 to 50 ), finally, we get about 200 of the number of requests per second (that is, the access is successful), and then adjust the stress multiplier (......) When it is adjusted to 10, there are 2 requests per second, but after it is adjusted to 12, there are 600 requests per second ...... In this process, I will be patient (in fact, I don't want to think about it ......) Once again (20 seconds warm-up, 5 minutes of testing), and finally, the sudden inspiration made me understand that the extra 600 times were actually 500 errors, that is, my application has a problem .................. This was originally very simple, and the result was a waste of time because I didn't want to think about it carefully.
Was is quite fun. I hope I can use it very well.
