(summary) Webbench of Web Performance Stress Testing Tools _ Program Language

PS: Stress testing is an important task in operation and maintenance. For example, before a Web site online, can withstand the number of visits, in the case of large traffic performance, these data indicators will directly affect the user experience. However, there is a common in stress testing, that is, the results of the stress test and the actual load will not be exactly the same, even if the pressure test is done well, can not guarantee 100% and online performance indicators the same. Faced with these problems, we can only try to find ways to simulate. Therefore, the stress test is very necessary, with these data, we can do the maintenance of their own platform to have a good idea.

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

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

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

Official Introduction:

The 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 isn't very realistic but it can test if your HTTPD can realy handle that many clients in once (try to run Some cgis) without taking your machine down. Displays Pages/min and bytes/sec. Can is used in the 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 http://192.168.80.157/phpinfo.php
webbench-c Concurrency number-t run test time URL

Apache Test Instance results:
When concurrency is 300,
Root [~]# webbench-c 300-t 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 transmitted per second 20794612 bytes/sec.

When concurrency is 1000, it has been shown that 87 connections have been failed, indicating overload.

Root [~]# webbench-c 1000-t 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
1000 clients, running Sec.

speed=24920 pages/min, 21037312 bytes/sec.
requests:24833 Susceed, failed.

Concurrency 1000 run 60 seconds after the number of TCP connections generated more than 12,000:

Summarize:
1, the pressure test work should be put on the product before the line, but not after the on-line;
2, test concurrency should be gradually increased by small, such as the concurrent 100 when observing the site load is how much, open the page is fluent, concurrent 200 is how many, the Web site opened slowly when the concurrency is how much, the site is not open when the concurrency is how much;
3, a more detailed test of a page, such as the electrical business site can focus on testing shopping carts, promotional pages, etc., because these pages account for a larger proportion of the total site traffic.