Apache Bench Tool

25th February 2008 - 4 minutes read time

Note: This post is over a year old and so the information contained here might be out of date. If you do spot something please leave a comment and we will endeavour to correct.

The Apache Bench tool can be found in the bin directory of any standard instillation of the Apache HTTP server. It can be used to test the response times of any web server you want and can be useful if you want to stress test a mission critical server before it goes live.

To use the tool open a command prompt (or terminal), navigate the Apache bin folder and find the program ab, this is the Apache Bench tool. The simplest form of running the tool is to use a single URL. However, you must enter a full file name or the tool will give you an invalid URL error.

ab http://www.google.com/index.html

This gives the following output.

Benchmarking www.google.com (be patient).....done
 
Server Software:        gws
Server Hostname:        www.google.com
Server Port:            80
 
Document Path:          /index.html
Document Length:        231 bytes
 
Concurrency Level:      1
Time taken for tests:   0.94090 seconds
Complete requests:      1
Failed requests:        0
Write errors:           0
Non-2xx responses:      1
Total transferred:      590 bytes
HTML transferred:       231 bytes
Requests per second:    10.63 [#/sec] (mean)
Time per request:       94.090 [ms] (mean)
Time per request:       94.090 [ms] (mean, across all concurrent requests)
Transfer rate:          0.00 [Kbytes/sec] received
 
Connection Times (ms)
                    min  mean[+/-sd] median   max
Connect:       41   41   0.0     41      41
Processing:    52   52   0.0     52      52
Waiting:       51   51   0.0     51      51
Total:         93   93   0.0     93      93

In this example, the tool has made a single request to the Google server. Apache Bench can be made to complete multiple, concurrent requests to the server with the addition of two flags. The first flag is -n, which is used to tell Apache Bench how many tests it should run, if the number 5 is used, the tool will repeat itself 5 times. The second flag is -c, which is used to tell Apache Bench how many concurrent connections should be made. The following example repeats the original test, but this time uses the -n and -c flags to run the tests 10 times, with 10 connections each time.

ab -n 10 -c 10 http://www.google.com/index.html

This produced the following output.

Benchmarking www.google.com (be patient).....done
 
Server Software:        gws
Server Hostname:        www.google.com
Server Port:            80
 
Document Path:          /index.html
Document Length:        231 bytes
 
Concurrency Level:      10
Time taken for tests:   0.229686 seconds
Complete requests:      10
Failed requests:        0
Write errors:           0
Non-2xx responses:      10
Total transferred:      5900 bytes
HTML transferred:       2310 bytes
Requests per second:    43.54 [#/sec] (mean)
Time per request:       229.686 [ms] (mean)
Time per request:       22.969 [ms] (mean, across all concurrent requests)
Transfer rate:          21.77 [Kbytes/sec] received
 
Connection Times (ms)
                    min  mean[+/-sd] median   max
Connect:       41   55   9.1     55      68
Processing:    54  100  37.9     87     164
Waiting:       51   97  37.8     83     159
Total:         95  155  43.9    149     229
 
Percentage of the requests served within a certain time (ms)
  50%    149
  66%    175
  75%    189
  80%    210
  90%    229
  95%    229
  98%    229
  99%    229
 100%    229 (longest request)

When running the tool on your own server you will rarely see times like this. For example, when running the tool with the same parameters on a local server with a standard Wordpress install it longest request time was 4227.

To find out a list of the options available just type in the following.

ab -h

test

Apache

Comments

Permalink

Good article about ApacheBench http://plutov.by/post/apache_bench_easy_tool

Permalink

Yeah, it's a pretty good article, althought it is in Russian...

Google translate seems to do the job though :)

Add new comment

Related Content

Allowing Cached HTTPS Traffic From Drupal With Varnish And Pound

Varnish is a web application accelerator that helps to speed up websites. It works by sitting in front of the web server and caching web pages that are served by it.

When a request for a web page is made Varnish passes this request on to the web server, which then responds to the request as it normally would. Varnish then caches the result of this request before sending it to the user.

Speeding Up Apache And Drupal With Varnish

Varnish is a web application accelerator that provides an easy speed increase to most web applications and Drupal is no exception. It works by creating a reverse proxy service that sits in front of your web server and caches traffic that comes through it. When the page is requested, Varnish forwards the request to the web server to complete the request, the response that comes back from the web server is then cached by Varnish. This means that the next request to the same page is served by Varnish and not the web server, which results in a large speed increase.

Adding iptables Rules With Ansible

Many systems and applications require certain access to certain ports and protocols. When installing these systems using Ansible it is necessary to also open up the needed ports so that the systems can function correctly. As there is no iptables module in Ansible the shell command is needed to add the iptables rules.

As an example, here is a task that adds a iptables rule to allow Apache to communicate on port 80.

Turning Off Apache Basic Authentication For A Single Directory

When setting up staging sites or similar I often add a simple Apache authentication check in order to stop everyone from viewing the site. This is also useful in stopping search engine spiders from accessing a site with testing content on it, which generally causes trouble. It isn't amazingly secure, but it keeps almost everyone out.

Using Phing To Create Apache Virtual Hosts

Phing is an awesome tool for automating things and I use it more and more for automating all kinds of different tasks. One of the tasks that I don't tend to do all that much is setting up a new local virtual host for Apache on my development machines. I know how to do it, but there is always something I forget to do, or a convention that I don't follow which means that I have to repeat myself at a later date to fix something I have missed.

IE8 Downloading docx Files As zip On Apache

I recently built a Drupal site on an Apache server setup and everything seemed fine until someone running IE8 tried to download a .docx file. For some reason IE8 insisted that this file was a .zip file and would open it as such, causing a bit of confusion as to what the problem was. I assumed that this was due to the mime type of the file not being set properly, but I decided to do a quick search to see if I could find anything to corroborate this. I thought it might be something odd that IE8 was doing as everything else was downloading the file perfectly.