简单模拟一下ab压力测试

时间:2023-03-10 01:08:14
简单模拟一下ab压力测试

在学习ab工具之前,我们需了解几个关于压力测试的概念

吞吐率(Requests per second)
概念:服务器并发处理能力的量化描述,单位是reqs/s,指的是某个并发用户数下单位时间内处理的请求数。某个并发用户数下单位时间内能处理的最大请求数,称之为最大吞吐率。
计算公式:总请求数 / 处理完成这些请求数所花费的时间,即
Request per second = Complete requests / Time taken for tests

并发连接数(The number of concurrent connections)
概念:某个时刻服务器所接受的请求数目,简单的讲,就是一个会话。

并发用户数(The number of concurrent users,Concurrency Level)
概念:要注意区分这个概念和并发连接数之间的区别,一个用户可能同时会产生多个会话,也即连接数。

用户平均请求等待时间(Time per request)
计算公式:处理完成所有请求数所花费的时间/ (总请求数 / 并发用户数),即
Time per request = Time taken for tests /( Complete requests / Concurrency Level)

服务器平均请求等待时间(Time per request: across all concurrent requests)
计算公式:处理完成所有请求数所花费的时间 / 总请求数,即
Time taken for / testsComplete requests
可以看到,它是吞吐率的倒数。
同时,它也=用户平均请求等待时间/并发用户数,即
Time per request / Concurrency Level

简单了解下ab

ab全程是apache benchmark,是apache官方推出的一个工具,创建多个并发访问线程,模拟多个访问者同时对一个URL地址进行访问。它的测试目标是基于URL的,因此它既可以来测试apache的负载压力,也可以测试Nginx等服务器的压力。

ab压力测试需要注意哪些?

测试的注意事项:
测试机器与被测试机器要分开,别在同一台机器上测试,否则结果是不准确的
不要对线上的服务器做测试,否则挂了就不好了哦。
观察测试工具ab所在的机器,以及被测试的前端机器的CPU,内存,网络等都不超过最高限度的75%。

下面测试下,两台服务器。

192.168.136.135  作为被测试的WEB服务器

192.168.136.148  作为ab测试的服务器

首先确保ab测试服务器安装ab,使用以下命令yum安装

yum install -y ab  //安装

安装完成之后,执行ab命令,返回一些帮助信息,确保安装成功

简单模拟一下ab压力测试

访问以下被测试的服务器,确保正常

简单模拟一下ab压力测试

执行下面的命令进行测试

ab -c  -n  http://192.168.136.135/phpinfo.php      //模拟100个并发数,总共访问5000次

返回的结果

This is ApacheBench, Version 2.3 <$Revision:  $>
Copyright Adam Twiss, Zeus Technology Ltd, http://www.zeustech.net/
Licensed to The Apache Software Foundation, http://www.apache.org/ Benchmarking 192.168.136.135 (be patient)
Completed requests
Completed requests
Completed requests
Completed requests
Completed requests
Completed requests
Completed requests
Completed requests
Completed requests
Completed requests
Finished requests Server Software: nginx //被测试的服务器是Nginx
Server Hostname: 192.168.136.135 //Hostname
Server Port: //端口 Document Path: /phpinfo.php //path
Document Length: bytes //文档大小 Concurrency Level: //100个并发
Time taken for tests: 11.860 seconds //时间花费
Complete requests: //请求了5000次
Failed requests: //失败了486次
(Connect: , Receive: , Length: , Exceptions: )
Write errors:
Total transferred: bytes //整个场景中的网络传输量
HTML transferred: bytes ///整个场景中的HTML内容传输量
Requests per second: 421.60 [#/sec] (mean) //QPS值,不高 吞吐率,大家最关心的指标之一,相当于 LR 中的每秒事务数,后面括号中的 mean 表示这是一个平均值
Time per request: 237.194 [ms] (mean) ///用户平均请求等待时间,大家最关心的指标之二,相当于 LR 中的平均事务响应时间,后面括号中的 mean 表示这是一个平均值
Time per request: 2.372 [ms] (mean, across all concurrent requests) //服务器平均请求处理时间,大家最关心的指标之三
Transfer rate: 39876.53 [Kbytes/sec] received //平均每秒网络上的流量,可以帮助排除是否存在网络流量过大导致响应时间延长的问题 Connection Times (ms)
min mean[+/-sd] median max
Connect: 1.3
Processing: 44.2
Waiting: 40.7
Total: 44.0 Percentage of the requests served within a certain time (ms)
% //这是每个请求处理的时间分布情况,平均页面的响应时间是232毫秒以内,66%的在238毫秒以内,主要看90%的处理时间
%
%
%
%
%
%
%
% (longest request) //最长是540毫秒

把并发数改为50测试一下

ab -c  -n  http://192.168.136.135/phpinfo.php
.....
Connection Times (ms)
min mean[+/-sd] median max
Connect: 1.3
Processing: 13.2
Waiting: 8.1
Total: 13.3 Percentage of the requests served within a certain time (ms)
% 104
%
%
%
%
%
%
%
% (longest request)
[root@localhost ~]# ab -c -n http://192.168.136.135/phpinfo.php
This is ApacheBench, Version 2.3 <$Revision: $>
Copyright Adam Twiss, Zeus Technology Ltd, http://www.zeustech.net/
Licensed to The Apache Software Foundation, http://www.apache.org/ Benchmarking 192.168.136.135 (be patient)
Completed requests
Completed requests
Completed requests
Completed requests
Completed requests
Completed requests
Completed requests
Completed requests
Completed requests
Completed requests
Finished requests Server Software: nginx
Server Hostname: 192.168.136.135
Server Port: Document Path: /phpinfo.php
Document Length: bytes Concurrency Level:
Time taken for tests: 10.987 seconds
Complete requests:
Failed requests:
(Connect: , Receive: , Length: , Exceptions: )
Write errors:
Total transferred: bytes
HTML transferred: bytes
Requests per second: 455.07 [#/sec] (mean) //QPS
Time per request: 109.874 [ms] (mean)
Time per request: 2.197 [ms] (mean, across all concurrent requests)
Transfer rate: 43023.80 [Kbytes/sec] received Connection Times (ms)
min mean[+/-sd] median max
Connect: 0.9
Processing: 14.4
Waiting: 10.1
Total: 14.3 Percentage of the requests served within a certain time (ms)
%
%
%
%
%
%
%
%
% (longest request) //最长193

测试结果其实并不实际很准确,因为测试机和被测试机都在一台机器上。这里值是了解。

然后再来一个静态的html测试下

简单模拟一下ab压力测试

ab -c  -n  http://192.168.136.135/ab.html

很快完成测试

Server Software:        nginx
Server Hostname: 192.168.136.135
Server Port: Document Path: /ab.html
Document Length: bytes Concurrency Level:
Time taken for tests: 0.830 seconds
Complete requests:
Failed requests: //0次失败
Write errors:
Total transferred: bytes
HTML transferred: bytes
Requests per second: 6024.71 [#/sec] (mean) //QPS达到了6000+
Time per request: 16.598 [ms] (mean)
Time per request: 0.166 [ms] (mean, across all concurrent requests)
Transfer rate: 1461.36 [Kbytes/sec] received Connection Times (ms)
min mean[+/-sd] median max
Connect: 1.4
Processing: 1.6
Waiting: 1.5
Total: 1.8 Percentage of the requests served within a certain time (ms)
% //响应也很快
%
%
%
%
%
%
%
% (longest request)

所以静态和动态的对比,不但要考虑到服务器的性能,还要考虑到程序的优化。

关于登录的问题
有时候进行压力测试需要用户登录,怎么办?
请参考以下步骤:

先用账户和密码登录后,用开发者工具找到标识这个会话的Cookie值(Session ID)记下来

如果只用到一个Cookie,那么只需键入命令:
ab -n 100 -C key=value http://test.com/

如果需要多个Cookie,就直接设Header:
ab -n 100 -H “Cookie: Key1=Value1; Key2=Value2” http://test.com/