WebBench installation and testing

In software testing work, stress testing is a very important job. For example, before a website goes online, how much traffic can it withstand, and how is the software performance under heavy traffic? The quality of these data indicators will directly affect the user experience. However, there is a commonality in stress tests, that is, the results of the stress test will not be exactly the same as the actual load results. Even if the stress test is done well, it cannot be guaranteed to be 100% the same as the online performance indicators. Faced with these problems, we can only try our best to find ways to simulate. Therefore, stress testing is very necessary. With these data, we can know what we have done for the launch of our products.

1. Webbench is a very simple and easy-to-use web stress testing tool

. 2. Webbench can test the performance of different services on the same hardware and the running status of the same service on different hardware.

3. The standard test of webbench can show us two things about the server: the number of corresponding requests per second and the amount of data transmitted per second.

4. Webbench can not only have the ability to test static pages, but also test dynamic pages. It also supports static or dynamic performance testing of secure websites with SSL.

5. Webbench can simulate up to 30,000 concurrent connections to test the load capacity of the website.

6. Webbench installation
Note
: Prerequisites for installation: gcc and make yum -y install ctags
wget http://home.tiscali.cz/~cz210552/distfiles/webbench-1.5.tar.gz
tar -zvxf webbench-1.5 need to be installed .tar.gz
cd webbench-1.5
make && make install

7. How to use Webbench:
webbench -c 100 -t 60 http://www.google.com/
100 concurrent requests for 60 seconds

-c is the number of concurrency -t is the time (seconds)
Result:
Benchmarking: GET http://www.google. com/
100 clients, running 60 sec.

Speed=5426 pages/min, 177921 bytes/sec.
Requests: 5426 susceed, 0 failed. Number
of successes, number of failures and speed Instead of going online, try to test across the public network instead of the intranet. During the test, the concurrency should gradually increase from small to small. For example, when the concurrency is 100, observe the load of the website, whether the website can operate normally, and how much is it when the concurrency is 200. How much is the concurrency when the website opens slowly, and how much is the concurrency when the website cannot be opened?