As a qualified website architect, need to be able to carry the pressure of the whole website is very familiar with, only in this way can make a strategist, winning thousands.
In particular, before the launch of a new project, the first thing to do is to simulate the user access in a staging environment, so how much access can be sustained, and in high concurrency, the performance of Web services and server hardware?
We have to collect these data indicators. In order to make a correct assessment of the effect of user experience in the real environment after online.
However, in the stress test there is a common denominator, that is, the results of the stress test and the actual load results will not be identical, even if the pressure test work done better, there is no guarantee that the 100% and the same performance indicators on the line. Face these
Problem, we can only find ways to simulate. Therefore, the stress test is very necessary, with these data, we can be on the site of the overall architecture planning, upgrading the structure, post-operation to be aware of.
On-line environment, the commonly used Web site pressure measurement tool has webbench, AB (Apache bench), Tcpcopy, LoadRunner, Httpload and so on.
Software name Introduction Advantages and disadvantages
Developed by Lionbridge, webbench tests the number of requests per second and the amount of data transmitted per second while supporting static, dynamic, SSL, simple deployment, and static and dynamic testing. For small site stress tests (single example up to 30,000 concurrency)
AB (Apache bench) Apache comes with a stress test tool that is designed to test how many requests are processed per second for a site, see more for static stress testing, weaker features, and non-professional stress testing tools
Tcpcopy based on the underlying application request replication, can forward a variety of online requests to the test server, with distributed pressure testing function, the test data and actual production data is closer to the rising star, mainly for medium and large-scale pressure testing, all TCP-based packets can be tested.
LoadRunner pressure testing industry, can create virtual users, can simulate the user's real access process to record as a script, its test results are most realistic simulation most realistic, and can be independent unit testing, but the deployment configuration is more complex, requires professionals to be able.
Http_load is a performance testing tool based on the Linux platform, which is very small in size and only 100KB. It runs in parallel multiplexing to test the throughput and load of the Web server.
Of course, the above test software in a specific environment may not meet our needs, how to do? Can be done on the basis of the existing, a small transformation, such as "add gzip for benchmark function"
If you aspire to be a good site architect, the above benchmark tools, you need to spend a quantitative time to study well, the old adage "工欲善其事, its prerequisite", ax.
Words website Stress test
