Web server performance/stress testing tool http_load

Http_load

The program is very small, and less than 100 kb after decompression

Http_load runs in Parallel Multiplexing to test the Web server throughput and load. However, unlike most stress testers

It can run in a single process and generally does not kill the client. You can also test https-type website requests.

: Http://soft.vpser.net/test/http_load/http_load-12mar2006.tar.gz
Easy to install
# Tar zxvf http_load-12mar2006.tar.gz
# Cd http_load-12mar2006
# Make & make install

Command Format: http_load-P concurrent access process count-s URL file to be accessed during access time

Parameters can be freely combined, and there is no limit between parameters. For example, if you write http_load-parallel 5-seconds

300 urls.txt is also supported. We will briefly describe the parameters.
-Parallel-P indicates the number of concurrent user processes.
-Fetches short-F: indicates the total number of visits
-Rate abbreviation-R: indicates the Access frequency per second.
-Seconds-S: indicates the total access time.

Prepare the URL File: urllist.txt. The file format is one URL per line. It is better to have more than 50-URLs. The file format is as follows:

Http://www.vpser.net/uncategorized/choose-vps.html
Http://www.vpser.net/vps-cp/hypervm-tutorial.html
Http://www.vpser.net/coupons/diavps-april-coupons.html
Http://www.vpser.net/security/vps-backup-web-mysql.html
For example:

Http_load-P 30-S 60 urllist.txt

The parameters are understood. Let's run a command to see its return results.
Command: %./http_load-rate 5-seconds 10 URLs indicates that a test lasts for 10 seconds and the frequency is 5.

49 fetches, 2 max parallel, 289884 bytes, in 10.0148 seconds 5916 mean Bytes/connection

4.89274 fetches/sec, 28945.5 Bytes/sec msecs/Connect: 28.8932 mean, 44.243 Max, 24.488 min

Msecs/first-response: 63.5362 mean, 81.624 Max, 57.803 minhttp Response codes: Code 200 -- 49

Result Analysis:

1.49 fetches, 2 max parallel, 289884 bytes, in 10.0148 seconds
In the preceding test, 49 requests are run, the maximum number of concurrent processes is 2, the total data transmitted is 289884 bytes, and the running time is 10.0148 seconds.
2.5916 mean Bytes/connection indicates that the average data volume transmitted by each connection is 289884/49 = 5916
3.4.89274 fetches/sec, 28945.5 Bytes/sec
The number of response requests per second is 4.89274, and the amount of data transmitted per second is 28945.5 Bytes/sec.
4. msecs/Connect: 28.8932 mean, 44.243 Max, 24.488 min indicates that the average response time for each connection is 28.8932 msecs, the maximum response time is 44.243 msecs, and the minimum response time is 24.488 msecs.
5. msecs/first-response: 63.5362 mean, 81.624 Max, 57.803 min
6. HTTP Response codes: Code 200 -- 49 indicates the type of the response page to be opened. If there are too many 403 types, you may need to check whether the system has encountered a bottleneck.