ab网站压力测试命令

我们知道压力测试的软件确实很多，诸如微软的wast，惠普的loadrunner以及等等其他的，但这些软件学习起来还是需要花费些时间，在选择上实在头痛，后来在郭欣的那本《构建高性能web站点》上看到了他介绍的这款apache自带的压力测试工具ab，十分喜爱，于是今天终于有机会体验下ab对网站的压力测试。 实验之前我的apache已经安装了，操作系统：ubuntu 10.04 vmware 7.0

1、先查看一下版本信息 ab -v（注意是大写的v）

studiogang@studiogang:~$ ab -v 
this is apachebench, version 2.3 <$revision: 655654 $> 
copyright 1996 adam twiss, zeus technology ltd, http://www.zeustech.net/ 
licensed to the apache software foundation, http://www.apache.org/ 

 2、我们也可以使用小写的v查看下ab命令的一些属性 ab -v

studiogang@studiogang:~$ ab -v 
ab: option requires an argument -- v 
ab: wrong number of arguments 
usage: ab [options] [http[s]://]hostname[:port]/path 
options are: 
 -n requests  number of requests to perform 
 -c concurrency number of multiple requests to make 
 -t timelimit seconds to max. wait for responses 
 -b windowsize size of tcp send/receive buffer, in bytes 
 -p postfile  file containing data to post. remember also to set -t 
 -u putfile  file containing data to put. remember also to set -t 
 -t content-type content-type header for posting, eg. 
     'application/x-www-form-urlencoded' 
     default is 'text/plain' 
 -v verbosity how much troubleshooting info to print 
 -w    print out results in html tables 
 -i    use head instead of get 
 -x attributes string to insert as table attributes 
 -y attributes string to insert as tr attributes 
 -z attributes string to insert as td or th attributes 
 -c attribute add cookie, eg. 'apache=1234. (repeatable) 
 -h attribute add arbitrary header line, eg. 'accept-encoding: gzip' 
     inserted after all normal header lines. (repeatable) 
 -a attribute add basic www authentication, the attributes 
     are a colon separated username and password. 
 -p attribute add basic proxy authentication, the attributes 
     are a colon separated username and password. 
 -x proxy:port proxyserver and port number to use 
 -v    print version number and exit 
 -k    use http keepalive feature 
 -d    do not show percentiles served table. 
 -s    do not show confidence estimators and warnings. 
 -g filename  output collected data to gnuplot format file. 
 -e filename  output csv file with percentages served 
 -r    don't exit on socket receive errors. 
 -h    display usage information (this message) 
 -z ciphersuite specify ssl/tls cipher suite (see openssl ciphers) 
 -f protocol  specify ssl/tls protocol (ssl2, ssl3, tls1, or all) 

3、现在我们就对51cto的网站进行一次压力测试吧，使用命令ab -n1000 -c10 http://www.jb51.net/index.php，其中 -n1000 表示总请求数 -c10表示并发用户数为10 http://www.jb51.net/index.php 表示请求的url，下面是测试的结果，其中我们最关心的三个指标，我已经注释出来了。

studiogang@studiogang:~$ ab -n1000 -c10 http://www.51cto.com/index.php 
this is apachebench, version 2.3 <$revision: 655654 $> 
copyright 1996 adam twiss, zeus technology ltd, http://www.zeustech.net/ 
licensed to the apache software foundation, http://www.apache.org/ 
 
 
benchmarking www.51cto.com (be patient) 
completed 100 requests 
completed 200 requests 
completed 300 requests 
completed 400 requests 
completed 500 requests 
completed 600 requests 
completed 700 requests 
completed 800 requests 
completed 900 requests 
completed 1000 requests 
finished 1000 requests 
 
 /*web服务器用的是nginx*/
server software:  nginx 
server hostname:  www.51cto.com 
server port:   80 
 
document path:   /index.php 
document length:  154 bytes 
 
concurrency level:  10 
time taken for tests: 74.373 seconds 
complete requests:  1000 
failed requests:  0 
write errors:   0 
non-2xx responses:  1000 
total transferred:  330000 bytes 
html transferred:  154000 bytes
/*大家最关心的指标之一，指的是吞吐率
相当于 lr 中的 每秒事务数 ，后面括号中的 mean 表示这是一个平均值*/ 
requests per second: 13.45 [#/sec] (mean)
/*大家最关心的指标之二，指的是用户平均请求等待时间
相当于 lr 中的 平均事务响应时间 ，后面括号中的 mean 表示这是一个平均值*/ 
time per request:  743.726 [ms] (mean) 
/*大家最关心的指标之三，指的是服务器平均请求处理时间
time per request:  74.373 [ms] (mean, across all concurrent requests) 
transfer rate:   4.33 [kbytes/sec] received 
 
connection times (ms) 
    min mean[+/-sd] median max 
connect:  129 163 245.3 145 3154 
processing: 129 576 1510.8 147 11756 
waiting:  129 567 1502.0 147 11756 
total:  261 739 1543.7 294 11888 
 
percentage of the requests served within a certain time (ms) 
 50% 294 
 66% 297 
 75% 304 
 80% 308 
 90% 1290 
 95% 3452 
 98% 7582 
 99% 7962 
 100% 11888 (longest request) 

4、为了使结果更有对比性，我们将并发用户更改为100个进行压力测试，我这里只将三个指标贴出来。

requests per second: 190.95 [#/sec] (mean) 
time per request:  523.694 [ms] (mean) 
time per request:  5.237 [ms] (mean, across all concurrent requests) 

5、将并发用户改为200个进行测试

requests per second: 186.00 [#/sec] (mean) 
time per request:  1149.433 [ms] (mean) 
time per request:  5.747 [ms] (mean, across all concurrent requests) 

6、500个并发用户时的情况

requests per second: 180.99 [#/sec] (mean) 
time per request:  2631.662 [ms] (mean) 
time per request:  5.263 [ms] (mean, across all concurrent requests) 

     我们来分析下测试的结果，先对比下吞吐率，当并发用户的时候吞吐率最高为190 reqs/s,当并发用户数为200,500 吞吐率下降了，随之用户的等待时间更是明显增加了，已经有2s的等待时间了。这说明性能明显下降了。当然分析这个测试结果并不是说明51cto的网站的并发用户只能在500左右，因为我是在服务器负荷的情况下就行测试的，这显然不能说明问题。另外我们在生产环境下测试的时候，最好能将测试结果做成报表，这样可以非常清晰地对比出问题来，好了，我该准备下，给上面提交一份我们公司网站的测试报告了。