Apache HTTP Server Version 2.2
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.
ab
[ -A auth-username:password ]
[ -b windowsize ]
[ -c concurrency ]
[ -C cookie-name=value ]
[ -d ]
[ -e csv-file ]
[ -f protocol ]
[ -g gnuplot-file ]
[ -h ]
[ -H custom-header ]
[ -i ]
[ -k ]
[ -n requests ]
[ -p POST-file ]
[ -P proxy-auth-username:password ]
[ -q ]
[ -r ]
[ -s ]
[ -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
:
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
-c concurrency
-C cookie-name=value
Cookie:
line to the request. The argument is
typically in the form of a name=value
pair. This field is repeatable.-d
-e csv-file
-f protocol
-g gnuplot-file
-h
-H custom-header
"Accept-Encoding: zip/zop;8bit"
).-i
HEAD
requests instead of GET
.-k
-n requests
-p POST-file
-T
.-P proxy-auth-username:password
:
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
ab
outputs a
progress count on stderr
every 10% or 100 requests or so. The
-q
flag will suppress these messages.-r
-s
ab -h
will show you) use the SSL
protected https
rather than the http
protocol.
This feature is experimental and very rudimentary. You probably
do not want to use it.-S
-t timelimit
-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
application/x-www-form-urlencoded
.
Default: text/plain
.-u PUT-file
-T
.-v verbosity
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
-x <table>-attributes
<table>
. Attributes
are inserted <table here >
.-X proxy[:port]
-y <tr>-attributes
<tr>
.-z <td>-attributes
<td>
.-Z ciphersuite
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 inputs, 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)
shows up top
in profile, which might indicate a performance problem; i.e., you
would measure the ab
performance rather than the server's.