Start using wrk instead of ab for all benchmarks about raspberry-pi-dramble HOT 2 CLOSED

$ wrk -t4 -c100 -d30 http://pidramble.com/about
Running 30s test @ http://pidramble.com/about
  4 threads and 100 connections
  Thread Stats   Avg      Stdev     Max   +/- Stdev
    Latency    81.71ms  167.94ms 672.44ms   90.24%
    Req/Sec     0.88k   424.31     3.07k    80.13%
  102027 requests in 30.00s, 669.82MB read
Requests/sec:   3400.89
Transfer/sec:     22.33MB

$ wrk -t4 -c4 -d10 http://pidramble.com/about?nocache=true
Running 10s test @ http://pidramble.com/about?nocache=true
  4 threads and 4 connections
  Thread Stats   Avg      Stdev     Max   +/- Stdev
    Latency   236.36ms   84.98ms 515.88ms   56.00%
    Req/Sec     3.96      1.54     7.00     58.67%
  177 requests in 10.02s, 1.16MB read
Requests/sec:     17.67
Transfer/sec:    118.63KB

Note: It takes a little more configuration to use wrk with cookies...

$ wrk -t4 -c100 -d30 http://pidramble.com/about
Running 30s test @ http://pidramble.com/about
  4 threads and 100 connections
  Thread Stats   Avg      Stdev     Max   +/- Stdev
    Latency    65.41ms   28.85ms 147.46ms   73.17%
    Req/Sec   387.76     47.92   457.00     66.77%
  46683 requests in 30.00s, 304.74MB read
Requests/sec:   1555.94
Transfer/sec:     10.16MB

$ wrk -t1 -c100 -d10 http://pidramble.com/about?nocache=true
Running 10s test @ http://pidramble.com/about?nocache=true
  1 threads and 100 connections
  Thread Stats   Avg      Stdev     Max   +/- Stdev
    Latency     5.59s     2.16s    8.97s    71.67%
    Req/Sec    11.00      0.00    11.00    100.00%
  108 requests in 10.02s, 720.62KB read
  Socket errors: connect 0, read 0, write 0, timeout 320
Requests/sec:     10.77
Transfer/sec:     71.88KB