New Droplet under performs on ApacheBench

September 24, 2014 2k views

I’m confused. Can somebody help me shed some light on this.

I created a new droplet and my ApacheBench(marks) aren’t on par with my previous Droplet. It always seems to stall on the last set of requests. I’ve done 400, 500, and 300 – all of them with the same results: stalls on the final 100 set before finishing resulting in a > 7 second total test run… That’s not right.

ab -n 500 -c 100 http://107.170.246.53/

Can somebody help me shed some light as to why?

If it was a Droplet resources, 300 should have worked given 500 stalled after completing 400. This was not the case.

I have a second Droplet, tier two, and it doesn’t exhibit this.

Test Results:

gp$ ab -n 500 -c 100 http://107.170.246.53/
This is ApacheBench, Version 2.3 <$Revision: 655654 $>
Copyright 1996 Adam Twiss, Zeus Technology Ltd, http://www.zeustech.net/
Licensed to The Apache Software Foundation, http://www.apache.org/

Benchmarking 107.170.246.53 (be patient)
Completed 100 requests
Completed 200 requests
Completed 300 requests
Completed 400 requests  (stalls here before completing 500)
Completed 500 requests
Finished 500 requests


Server Software:        lighttpd/1.4.33
Server Hostname:        107.170.246.53
Server Port:            80

Document Path:          /
Document Length:        2886 bytes

Concurrency Level:      100
Time taken for tests:   7.945 seconds
Complete requests:      500
Failed requests:        0
Write errors:           0
Total transferred:      1535948 bytes
HTML transferred:       1444265 bytes
Requests per second:    62.93 [#/sec] (mean)
Time per request:       1588.995 [ms] (mean)
Time per request:       15.890 [ms] (mean, across all concurrent requests)
Transfer rate:          188.79 [Kbytes/sec] received

Connection Times (ms)
              min  mean[+/-sd] median   max
Connect:       13   24   4.3     23      37
Processing:    30  276 1145.3    101    7920
Waiting:       27  275 1145.3    100    7919
Total:         48  300 1146.4    124    7944

Percentage of the requests served within a certain time (ms)
  50%    124
  66%    133
  75%    145
  80%    153
  90%    160
  95%    187
  98%   7928
  99%   7936
 100%   7944 (longest request)
hermes:tracking gp$ ab -n 300 -c 100 http://107.170.246.53/
This is ApacheBench, Version 2.3 <$Revision: 655654 $>
Copyright 1996 Adam Twiss, Zeus Technology Ltd, http://www.zeustech.net/
Licensed to The Apache Software Foundation, http://www.apache.org/

Benchmarking 107.170.246.53 (be patient)
Completed 100 requests
Completed 200 requests (stalls here, before completing 300)
Completed 300 requests
Finished 300 requests


Server Software:        lighttpd/1.4.33
Server Hostname:        107.170.246.53
Server Port:            80

Document Path:          /
Document Length:        2886 bytes

Concurrency Level:      100
Time taken for tests:   7.881 seconds
Complete requests:      300
Failed requests:        0
Write errors:           0
Total transferred:      920700 bytes
HTML transferred:       865800 bytes
Requests per second:    38.07 [#/sec] (mean)
Time per request:       2626.977 [ms] (mean)
Time per request:       26.270 [ms] (mean, across all concurrent requests)
Transfer rate:          114.09 [Kbytes/sec] received

Connection Times (ms)
              min  mean[+/-sd] median   max
Connect:       17   25   5.2     23      42
Processing:    29  375 1452.0     96    7850
Waiting:       26  374 1451.9     96    7849
Total:         47  399 1453.6    119    7880

Percentage of the requests served within a certain time (ms)
  50%    119
  66%    125
  75%    127
  80%    129
  90%    144
  95%    167
  98%   7872
  99%   7878
 100%   7880 (longest request)
1 Answer

Never mind. If I could close this, I would. It appears, after an evening settling, things are now working.

I am still bothered as to why this happened to being with. However, tests run successfully now. I’ll leave it at that.

Have another answer? Share your knowledge.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!