Dear:friends
Some days ago a friend asked me, what is the performance test, why do the performance test, do the system performance test for what, and now the server is also cheaper, you can increase the machine at any time, do the cluster, no more than you do performance testing to come faster, the effect is better.
So many problems suddenly popped up in my brain, when the CPU couldn't handle it. The stand-alone hangs out.
In fact, to do performance testing is nothing more than two points:
First, the user's perspective to observe the performance of the system, for example: Our common second kill activity, at a certain time, a specific number of n+ the user click the mouse, send the request, the server processing instantaneous processing capacity, and complete the process of response time. Satisfying a good user experience is the essence of our performance.
Second, to the technician's point of view of the system bottleneck, in the high concurrency, fast growth, clustered architecture system, testing system in the process of continuous pressure may occur system bottlenecks, and system problems, such as: when we test the Web system, the user's concurrency is 100Vuser, running time in 30 minutes, The system may have queue timeout, insufficient network bandwidth, server outage, database deadlock, thread deadlock, cpu,mem,i/o, and other bottlenecks, can be found and resolved in a timely manner.
In a good system environment, the capacity planning of the early warning mechanism to meet the current anticipated future readiness. This is the nature of why we do performance testing techniques.
This article is from the "surveillance Commands for SAR" blog, so be sure to keep this source http://rainbow9912.blog.51cto.com/9070528/1659362
Performance testing is the purpose