Web stress testing-Web stress testing, stress testing-webbench

Web stress testing-Web stress testing, stress testing-webbench

1. web tracking download, address: http://home.tiscali.cz /~ Cz210552/webbench.html

2. wen Yun Installation

[Root @ web111 tmp] # tar-zxvf webbench-1.5.tar.gz

[Root @ web111 tmp] # cd webbench-1.5

[Root @ vstar111 webbench-1.5] # ll
Total 28
Lrwxrwxrwx 1 1001 root 16 Nov 15 ChangeLog-> debian/changelog
Lrwxrwxrwx 1 1001 root 16 Nov 15 COPYRIGHT-> debian/copyright
Drwxr-xr-x 2 1001 root 4096 Jun 25 2004 debian
-Rw-r -- 1 1001 1001 1063 Jun 25 2004 Makefile
-Rw-r -- 1 1001 1001 1491 Jan 12 2004 socket. c
-Rw-r -- 1 1001 1001 2411 Jan 14 2004 webbench.1
-Rw-r -- 1 1001 1001 10978 Jun 25 2004 webbench. c

[Root @ web111 webbench-1.5] # make
Cc-Wall-ggdb-W-O-c-o webbench. o webbench. c
Webbench. c: In function 'arm _ handler ':
Webbench. c: 77: warning: unused parameter 'signal'
Cc-Wall-ggdb-W-O-o webbench. o
Ctags *. c
[Root @ web111 webbench-1.5] # make install
Install-s webbench/usr/local/bin
Install-m 644 webbench.1/usr/local/man/man1
Install-d/usr/local/share/doc/webbench
Install-m 644 debian/copyright/usr/local/share/doc/webbench
Install-m 644 debian/changelog/usr/local/share/doc/webbench

So far, installation is complete

3. Use

[Root @ web111 webbench-1.5] # man webbench

Contains detailed information such as syntax and parameters.

Tests:

[Root @ web111 webbench-1.5] # webbench-c 1024 http: // 10.244.170.110/
Webbench-Simple Web Benchmark 1.5
Copyright (c) Radim Kolar 1997-2004, GPL Open Source Software.

Benchmarking: GET http: // 10.244.170.110/
1024 clients, running 30 sec.
Speed = 103590 pages/min, 537553 bytes/sec.
Requests: 51795 susceed, 0 failed.

Tests:

[Root @ web111 webbench-1.5] # webbench-c 10240 http: // 10.244.170.110/
Webbench-Simple Web Benchmark 1.5
Copyright (c) Radim Kolar 1997-2004, GPL Open Source Software.

Benchmarking: GET http: // 10.244.170.110/
1024 clients, running 30 sec.

Speed = 93646 pages/min, 482920 bytes/sec.
Requests: 46559 susceed, 264 failed.

Comparing the two test results, we found that the second test was slow and the number of failures increased significantly;

Check the zabbix monitoring and compare the CPU usage. The cpu usage is very high during the test! After multiple tests, it is found that a large number of tests occupy a large amount of memory, resulting in a direct restart of the server.

Copy others' test benchmarks:

1. stress testing should be conducted before the product is launched, rather than after the launch;

2. During the test, it is best to enable the monitoring of the testing machine;

3. Try to perform the test across the public network instead of the Intranet;

4. The concurrency during testing should increase gradually from small to small. For example, when the concurrency is 100, check the website load and whether the website is open smoothly, what is concurrency 200, what is concurrency when the website is opened slowly, and what is concurrency when the website cannot be opened

5. unit tests should be conducted as much as possible. For example, B2C websites can focus on shopping carts and promotion pages, because these pages account for a large proportion of access to the entire website.