作者：烧鸡太子爷
起源：恒生 LIGHT 云社区
简介
往年公司开发者大会是线上的模式，依照常规，为了服务的保障，须要对整个零碎的性能做一个评估，长期抱佛脚，比拟罕用的工具有 jmeter 和 Apache Bench，最终在两者之间抉择了 Apache Bench(简称 ab)，也就针对 ab 工具做了一些总结。
AB 简介
关上官网能够看到上面一段话：
ab is a tool for benchmarking your Apache Hypertext Transfer Protocol (HTTP) server. It is designed to give you an impression
of how your current Apache installation performs. This especially shows you how many requests per second your Apache installation
is capable of serving.ApacheBench 是 Apache 服务器自带的一个 web 压力测试工具，简称 ab。ab 又是一个行工具，对发动负载的本机要求很低，依据 ab 能够创立很多的并发拜访线程，模仿多个访问者同时对某一 URL 地址进行拜访，因而能够用来测试指标服务器的负载压力。总的来说 ab 工具玲珑简略，上手学习较快，能够提供须要的根本性能指标，然而没有图形化后果，不能监控。
jmeter 和 ab 的比拟
这个网上有很多的介绍，收集找了一位大神的总结（具体的不多说，大家能够自行百度）
1、jmeter 是一次残缺的申请和返回，而 AB 只是收回去申请，并不对返回做解决，只是申请发送胜利或者失败。所以从准确性来说，Jmeter 更精确，而 AB 速度更快，能够用起码的机器资源产生更多的拜访申请；
2、Jmeter 自身反对断言、可变参数和 CSV 数据集的输出，能设定更加灵便多变的的测试场景，而 AB 则不反对（临时没想到）；
3、Jmeter 能够提供更加具体的统计后果数据，比方接口错误信息、单线程的申请工夫等，而 AB 则不反对；
4、Jmeter 不反对准确工夫的压测，比方压测 10 分钟，然而 AB 反对；
5、Jmeter 反对分布式的压测集群，且反对函数，AB 不反对；
6、软件本身消耗资源：Jmeter 因为比拟重，且统计了很多后果数据，比 AB 耗时消耗资源多，AB 属于超轻量级，在开发测试过程中非常适宜做单接口压测。
因为本次只针对单个接口做测试，手上刚好有闲暇的 linux 机器，综合思考就抉择了 AB，废话不多说，上面就进行 AB 的应用做一些解说。
AB 的应用
官网针对 ab 的应用做了很具体的介绍，咱们能够去查看官网地址：
https://httpd.apache.org/docs…
上面做了一些节抄，英文比较简单，就不做翻译了。
ab 参数
ab [-A auth-username:password] [-b windowsize] [-B local-address] [-c concurrency] [-C cookie-name=value] [-d]
[-e csv-file] [-E client-certificate file] [-f protocol] [-g gnuplot-file] [-h] [-H custom-header] [-i] [-k]
[-l] [-m HTTP-method] [-n requests] [-p POST-file] [-P proxy-auth-username:password] [-q] [-r] [-s timeout]
[-S] [-t timelimit] [-T content-type] [-u PUT-file] [-v verbosity] [-V] [-w] [-x <table>-attributes]
[-X proxy[:port] ] [-y <tr>-attributes] [-z <td>-attributes] [-Z ciphersuite] [http[s]://]hostname[:port]/path参数阐明
- -A auth-username:password
Supply BASIC Authentication credentials to the server. The username and password are separated by a single : and sent on the wire base64 encoded. The string is sent regardless of whether the server needs it (i.e., has sent an 401 authentication needed).- -b windowsize
Size of TCP send/receive buffer, in bytes.- -B local-address
Address to bind to when making outgoing connections.- -c concurrency
Number of multiple requests to perform at a time. Default is one request at a time.- -C cookie-name=value
Add a Cookie: line to the request. The argument is typically in the form of a name=value pair. This field is repeatable.- -d
Do not display the "percentage served within XX [ms] table". (legacy support).- -e csv-file
Write a Comma separated value (CSV) file which contains for each percentage (from 1% to 100%) the time (in milliseconds) it took to serve that percentage of the requests. This is usually more useful than the 'gnuplot' file; as the results are already 'binned'.- -E client-certificate-file
When connecting to an SSL website, use the provided client certificate in PEM format to authenticate with the server. The file is expected to contain the client certificate, followed by intermediate certificates, followed by the private key. Available in 2.4.36 and later.- -f protocol
Specify SSL/TLS protocol (SSL2, SSL3, TLS1, TLS1.1, TLS1.2, or ALL). TLS1.1 and TLS1.2 support available in 2.4.4 and later.- -g gnuplot-file
Write all measured values out as a 'gnuplot' or TSV (Tab separate values) file. This file can easily be imported into packages like Gnuplot, IDL, Mathematica, Igor or even Excel. The labels are on the first line of the file.- -h
Display usage information.- -H custom-header
Append extra headers to the request. The argument is typically in the form of a valid header line, containing a colon-separated field-value pair (i.e., "Accept-Encoding: zip/zop;8bit").- -i
Do HEAD requests instead of GET.- -k
Enable the HTTP KeepAlive feature, i.e., perform multiple requests within one HTTP session. Default is no KeepAlive.- -l
Do not report errors if the length of the responses is not constant. This can be useful for dynamic pages. Available in 2.4.7 and later.- -m HTTP-method
Custom HTTP method for the requests. Available in 2.4.10 and later.- -n requests
Number of requests to perform for the benchmarking session. The default is to just perform a single request which usually leads to non-representative benchmarking results.- -p POST-file
File containing data to POST. Remember to also set -T.- -P proxy-auth-username:password
Supply BASIC Authentication credentials to a proxy en-route. The username and password are separated by a single : and sent on the wire base64 encoded. The string is sent regardless of whether the proxy needs it (i.e., has sent an 407 proxy authentication needed).- -q
When processing more than 150 requests, ab outputs a progress count on stderr every 10% or 100 requests or so. The -q flag will suppress these messages.- -r
Don't exit on socket receive errors.- -s timeout
Maximum number of seconds to wait before the socket times out. Default is 30 seconds. Available in 2.4.4 and later.- -S
Do not display the median and standard deviation values, nor display the warning/error messages when the average and median are more than one or two times the standard deviation apart. And default to the min/avg/max values. (legacy support).- -t timelimit
Maximum number of seconds to spend for benchmarking. This implies a -n 50000 internally. Use this to benchmark the server within a fixed total amount of time. Per default there is no timelimit.- -T content-type
Content-type header to use for POST/PUT data, eg. application/x-www-form-urlencoded. Default is text/plain.- -u PUT-file
File containing data to PUT. Remember to also set -T.- -v verbosity
Set verbosity level - 4 and above prints information on headers, 3 and above prints response codes (404, 200, etc.), 2 and above prints warnings and info.- -V
Display version number and exit.- -w
Print out results in HTML tables. Default table is two columns wide, with a white background.- -x -attributes
String to use as attributes for table. Attributes are inserted table here.- -X proxy[:port]
Use a proxy server for the requests.- -y -attributes
String to use as attributes for tr.- -z -attributes
String to use as attributes for tb- -Z ciphersuite
Specify SSL/TLS cipher suite (See openssl ciphers)参数阐明
Server Software
The value, if any, returned in the server HTTP header of the first successful response. This includes all characters in the header from beginning to the point a character with decimal value of 32 (most notably: a space or CR/LF) is detected.
Server Hostname
The DNS or IP address given on the command line
Server Port
The port to which ab is connecting. If no port is given on the command line, this will default to 80 for http and 443 for https.
SSL/TLS Protocol
The protocol parameters negotiated between the client and server. This will only be printed if SSL is used.
Document Path
The request URI parsed from the command line string.
Document Length
This is the size in bytes of the first successfully returned document. If the document length changes during testing, the response is considered an error.
Concurrency Level
The number of concurrent clients used during the test
Time taken for tests
This is the time taken from the moment the first socket connection is created to the moment the last response is received
Complete requests
The number of successful responses received
Failed requests
The number of requests that were considered a failure. If the number is greater than zero, another line will be printed showing the number of requests that failed due to connecting, reading, incorrect content length, or exceptions.
Write errors
The number of errors that failed during write (broken pipe).
Non-2xx responses
The number of responses that were not in the 200 series of response codes. If all responses were 200, this field is not printed.
Keep-Alive requests
The number of connections that resulted in Keep-Alive requests
Total body sent
If configured to send data as part of the test, this is the total number of bytes sent during the tests. This field is omitted if the test did not include a body to send.
Total transferred
The total number of bytes received from the server. This number is essentially the number of bytes sent over the wire.
HTML transferred
The total number of document bytes received from the server. This number excludes bytes received in HTTP headers
Requests per second
This is the number of requests per second. This value is the result of dividing the number of requests by the total time taken
Time per request
The average time spent per request. The first value is calculated with the formula concurrency timetaken 1000 / done while the second value is calculated with the formula timetaken * 1000 / done
Transfer rate
The rate of transfer as calculated by the formula totalread / 1024 / timetaken
举例
从下面能够看到 ab 反对的参数很多，但其实咱们一般来说只有 -n（发送的申请总数）和 -c（申请的并发线程数）的参数是必要的。
从图上的列子咱们能够看出，本次是启动了 200 个线程并发，总共跑了 2000 次（为了防止泄露信息安全，对接口做了隐衷解决）。
后果咱们察看到
Requests for second 为 722.77, 即每秒钟解决 722.77 个申请；
Time per request 为 276.714, 即申请的均匀耗时为 276.714ms；
另外还能够 99 线，98 线，95 线等的耗时指标；
特地要留神，NON-2xx responses 为 2000，而申请总共 2000，则示意 2000 个申请返回的全部都是非 2000，须要思考申请返回是否都是谬误的；