Web Stress test Tool Webbench

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. So, the stress test is very necessary, with this data, we can do our own maintenance platform to be aware of

1. Introduction

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

Advantages:

• Up to 30,000 concurrent connections can be simulated to test the load capacity of the Web site

• Webbench can test the performance of different services on the same hardware, 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 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.

• This program is smaller and less than 50K after decompression

2. Download

1 [[Email protected] src]# wget http://files.cnblogs.com/files/vforbox/webbench-1.5.tar.gz

• can only be downloaded and accessed using the wget, Curl tools inside Linux

3. Installation

1 [[Email protected] src]# tar zxvf webbench-1.5.tar.gz2 [[email protected] src]# CD webbench-1.53 [[email protected] Webb ench-1.5]# make//execute makes, the Webbench executable is generated in the current directory

4, the use of Webbench

• Webbench-c Concurrent number-T run test time URL

1 [[Email protected] ~]webbench-c 1000-t http://192.168.1.187/phpinfo.php

• Apache Test Instance Results

When concurrency is 200
[Email protected] webbench-1.5]# webbench-c 200-t http://192.168.1.187/phpinfo.php
Webbench-simple Web Benchmark 1.5
Copyright (c) Radim Kolar 1997-2004, GPL Open Source software.

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

speed=47324 pages/min, 44176716 bytes/sec.
requests:23662 susceed, 0 failed.

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

When concurrency is 1000
[Email protected] webbench-1.5]# webbench-c 1000-t http://192.168.1.187/phpinfo.php
Webbench-simple Web Benchmark 1.5
Copyright (c) Radim Kolar 1997-2004, GPL Open Source software.

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

speed=48221 pages/min, -27471298 bytes/sec.
requests:47374 susceed, 847 failed.
When concurrency is 1000, 847 connection failed have been shown, which indicates a severe overload.

• More than 12,000 TCP connections generated after concurrent 1000 runs for 60 seconds

5. Summary

• Stress testing should be done before the product goes live, not on the go

• Test concurrency should be increased by small gradually, such as 100 when observing the Web site load is how much, open the page is fluent, and the number of concurrent 200, the Web site is slow when the concurrency is how many, the site is not open when concurrency is how much

• A more detailed test of a page, such as e-commerce website can focus on testing shopping carts, promotional pages, etc., because these pages account for the overall site traffic is large proportion

Reprint to: (Author: Xiao Ling Source: http://www.cnblogs.com/vforbox/)

Web Stress test Tool Webbench