After we completed the SPS2003-based development, we have realized our specific applications, can we directly ask users to use it? If I do this, then experienced developers will definitely nose to this: I don't even have pressure testing! Really don't want to live ...
hehe yes. The development environment often only considers the function. In the specific environment, you need to consider a lot of users to access, will many features will be wrong? What will performance? ...... Let's take a look at it, how to do pressure testing.
I believe that there is a lot of tools for pressure testing, and we are generally used, and now a lot is Application Center Test (ACT). This stuff is a formation in VS.NET, it is very simple, easy to get started, and support scripts, you can also achieve complex features ...
Here, the test step is omitted, suppose we only do testing a website directly, such as Test.sendRequest ("http://server/default.aspx"). How to analyze the results now?
Below is some information I just learned, sharing with everyone, I hope to have a friend who has experienced friends.
1. First, check and there is no error, such as 401 users do not have a verification error. If there is an error, then the result is definitely wrong, nor is it.
2. Analyze Average Requests Per Second, it should be "average average request per second".
We can test a few more times, use 1, 2, 5, 10, 50, 100, 200 ..., the number of concurrent browser connections. Then we can put several results in a chart to analyze.
Under normal circumstances, as the number of concurrent browser is increased, the number of Average Requests Per Second will also increase, but after a certain value, the Average Requests Per Second has dropped. So, this value is almost the maximum number of concurrent browser connections that the server can support.
3. Average Time To Last Byte
After the send request, the time to receive the server response.
Obviously, in general, as the number of concurrent browser is increased, this value will become large. In general, analyzing this value is reasonable, you can refer to the following criteria:
0.1 second: very fast
1 second: The speed is still very fast, basically no need to consider performance issues
3 - 4 seconds: a result for internal networks can be accepted
5 - 8 seconds: A result for external networks can be accepted
10 seconds or more: too slow
4. Average Time To First Byte
Like, it is only the time to send the request, and the time you receive the server response.
Welcome everyone to discuss, publish about ACT experience.
Posted on Tuesday, December 21, 2004 4:27 PM
