ab -c 30 -n 3000 http://www.blinklink.me/b/4XIxfoeF4C0
Concurrency Level: 30
Time taken for tests: 93.802 seconds
Complete requests: 3000
Failed requests: 2137
(Connect: 0, Receive: 0, Length: 2137, Exceptions: 0)
Write errors: 0
Requests per second: 31.98 [#/sec] (mean)
Time per request: 938.024 [ms] (mean)
Time per request: 31.267 [ms] (mean, across all concurrent requests)
Transfer rate: 182.47 [Kbytes/sec] received
Connection Times (ms)
min mean[+/-sd] median max
Connect: 116 165 165.9 122 1276
Processing: 137 771 624.6 625 6827
Waiting: 132 733 595.7 601 6823
Total: 254 936 644.7 789 7062
You're intentionally making it too generic to portray the guy as an asshole, when that's not how things went down. Very politician-like. Yuck.
I'm betting that version 2 will solve this problem.
(Edit: I added another 1000 views by tweeting, so it didn't affect it permanently)
* ab has more results variation between runs
* ab will almost always report lower performance than wrk
* If you have two implementations being benchmarked, A and B and B is always faster than A. wrk will report a greater degree of performance separation between A and B.
"Three Felonies a Day" via https://mailman.stanford.edu/pipermail/liberationtech/2013-J...
It lets you simulate hitting your web server to benchmark the speed. You can do cool things like test concurrent and sequential connections.
> ab - Apache HTTP server benchmarking tool
$ whatis ab
ab (1) - Apache HTTP server benchmarking tool
$ wtf ab
ab: ab (1) - Apache HTTP server benchmarking tool