# phpman > man > ab

> **TLDR:** Apache HTTP server benchmarking tool.
>
- Execute 100 HTTP GET requests to a given URL:
  `ab -n 100 {{url}}`
- Execute 100 HTTP GET requests, in concurrent batches of 10, to a URL:
  `ab -n 100 -c 10 {{url}}`
- Execute 100 HTTP POST requests to a URL, using a JSON payload from a file:
  `ab -n 100 -T {{application/json}} -p {{path/to/file.json}} {{url}}`
- Use HTTP [k]eep-Alive, i.e. perform multiple requests within one HTTP session:
  `ab -k {{url}}`
- Set the maximum number of seconds ([t]imeout) to spend for benchmarking (30 by default):
  `ab -t {{60}} {{url}}`
- Write the results to a CSV file:
  `ab -e {{path/to/file.csv}}`

*Source: tldr-pages*

---

[AB(1)](https://www.chedong.com/phpMan.php/man/AB/1/markdown)                                            ab                                            [AB(1)](https://www.chedong.com/phpMan.php/man/AB/1/markdown)



## NAME
       ab - Apache HTTP server benchmarking tool


## SYNOPSIS
       **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_



## SUMMARY
       **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 es‐
       pecially  shows you how many requests per second your Apache installation is capable of serv‐
       ing.



## OPTIONS
### -A
              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 re‐
              gardless of whether the server needs it (_i.e._, has sent an 401 authentication needed).

### -b
              Size of TCP send/receive buffer, in bytes.

### -B
              Address to bind to when making outgoing connections.

### -c
              Number of multiple requests to perform at a time. Default is one request at a time.

### -C
              Add a **Cookie:** line to the request.  The  argument  is  typically  in  the  form  of  a
              _name_=_value_ pair. This field is repeatable.

### -d

### -e
              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
              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 certifi‐
              cate, followed by intermediate certificates, followed by the private key. Available in
              2.4.36 and later.

### -f
              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
              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

### -H
              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

### -k
              session. Default is no KeepAlive.

### -l
              ful for dynamic pages. Available in 2.4.7 and later.

### -m
              Custom HTTP method for the requests. Available in 2.4.10 and later.

### -n
              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 re‐
              sults.

### -p
              File containing data to POST. Remember to also set **-T**.

### -P
              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
              10% or 100 requests or so. The **-q** flag will suppress these messages.

### -r

### -s
              Maximum number of seconds to wait before the socket times out. Default is 30  seconds.
              Available in 2.4.4 and later.

### -S
              messages when the average and median are more than one or two times the standard devi‐
              ation apart. And default to the min/avg/max values. (legacy support).

### -t
              Maximum  number  of  seconds to spend for benchmarking. This implies a **-n** **50000** inter‐
              nally. Use this to benchmark the server within a fixed total amount of time.  Per  de‐
              fault there is no timelimit.

### -T
              Content-type  header  to use for POST/PUT data, eg. **application/x-www-form-urlencoded**.
              Default is **text/plain**.

### -u
              File containing data to PUT. Remember to also set **-T**.

### -v
              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

### -w
              background.

### -x
              String to use as attributes for **<table>**. Attributes are inserted **<table** _here_ >.

### -X
              Use a proxy server for the requests.

### -y
              String to use as attributes for **<tr>**.

### -z
              String to use as attributes for **<td>**.

### -Z
              Specify SSL/TLS cipher suite (See openssl ciphers)


## OUTPUT
       The following list describes the values returned by **ab**:



       Server Software
              The value, if any, returned in the _server_ HTTP header  of  the  first  successful  re‐
              sponse. This includes all characters in the header from beginning to the point a char‐
              acter 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  re‐
              sponses 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**


## BUGS
       There are various statically declared buffers of fixed length. Combined with the lazy parsing
       of the command line arguments, the response headers from the server and  other  external  in‐
       puts, this might bite you.


       It  does  not  implement HTTP/1.x fully; only accepts some 'expected' forms of responses. The
       rather heavy use of [**strstr(3)](https://www.chedong.com/phpMan.php/man/strstr/3/markdown)** shows up top in profile, which  might  indicate  a  performance
       problem; _i.e._, you would measure the **ab** performance rather than the server's.




Apache HTTP Server                           2018-10-10                                        [AB(1)](https://www.chedong.com/phpMan.php/man/AB/1/markdown)
