(summary) Webbench of Web performance stress testing tools

PS: In operation and maintenance work, stress testing is a very important work. For example, before a website online, can withstand how much traffic, in the case of large traffic performance, these data indicators will directly affect the user experience. 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. Faced with these problems, we can only try to find ways to simulate. Therefore, stress testing is very necessary, with these data, we can do the maintenance of our platform to be aware of.

Webbench is a well-known website stress testing tool that was developed by Lionbridge Inc. (http://www.lionbridge.com).

Webbench can test the performance of different services on the same hardware, as well as the health of the same service on different hardware. The standard test of Webbench can show us two things about the server: the corresponding requests per second and the amount of data transferred per second. Webbench can not only have the ability to test the static pages, but also the ability to test dynamic pages (asp,php,java,cgi). And he supports static or dynamic performance testing of secure websites that contain SSL, such as e-commerce sites.
Webbench can simulate up to 30,000 concurrent connections to test the load capacity of the Web site.

Official homepage: http://home.tiscali.cz/~cz210552/webbench.html

Official Introduction:

Web Bench is very simple tool for benchmarking WWW or proxy servers. Uses fork() for simulating multiple clients and can use HTTP/0.9-HTTP/1.1 requests. This benchmark is not very realistic, but it can test if your HTTPD can realy handle that many clients at once (try to run some CGIs) without taking your machine down. Displays pages/min and bytes/sec. Can be used in more aggressive mode with -f switch.


1, Webbench Installation:

wget http://www.ha97.com/code/webbench-1.5.tar.gz
tar zxvf webbench-1.5.tar.gz
cd webbench-1.5
make
make install

2, Webbench use:
webbench -c 1000 -t 60 http://192.168.80.157/phpinfo.php
Webbench-c Concurrent number-T run test time URL

Apache Test Example results:
When concurrency is 300,
root [ ~ ]# webbench -c 300 -t 60 http://192.168.80.157/phpinfo.php
Webbench - Simple Web Benchmark 1.5
Copyright (c) Radim Kolar 1997-2004, GPL Open Source Software.

Benchmarking:get http://192.168.80.157/phpinfo.php
Clients, running Sec.

Speed=24525 pages/min, 20794612 bytes/sec.
Requests: 24525 susceed, 0 failed.

Response Requests per second: 24525 Pages/min, the amount of data transferred 20794612 bytes/sec per second.

When concurrency is 1000, there are 87 connections failed that indicate overload.

root [ ~ ]# webbench -c 1000 -t 60 http://192.168.80.157/phpinfo.php
Webbench - Simple Web Benchmark 1.5
Copyright (c) Radim Kolar 1997-2004, GPL Open Source Software.

Benchmarking:get http://192.168.80.157/phpinfo.php
Clients, running Sec.

Speed=24920 pages/min, 21037312 bytes/sec.
Requests: 24833 susceed, 87 failed.

The number of TCP connections generated after concurrent 1000 runs 60 seconds is more than 12,000:

Summarize:
1, the pressure test should be put on the product before the launch, rather than on-line after;
2, the test concurrency should be gradually increased by the small, such as 100 when observing the site load is how much, open the page is fluent, concurrency 200 is how much, the website is slow when the concurrency is how much, the site is not open when concurrency is how much;
3, a more detailed test of a page, such as e-commerce website can focus on testing shopping carts, promotional pages, etc., because these pages accounted for the overall site visits a large proportion.