Why the benchmark results are different?

[bigplum]

Hi, 

I install the newest nginx, and run 3 benchmark tools:
ab/http_load/weighttp. I get 
three rps results 9129.48/2594.08 /1107. So which tool give the right
result? 

# ab2 -n 10000 -c 1000 http://10.6.2.213/
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 10.6.2.213 (be patient)
Completed 1000 requests
Completed 2000 requests
Completed 3000 requests
Completed 4000 requests
Completed 5000 requests
Completed 6000 requests
Completed 7000 requests
Completed 8000 requests
Completed 9000 requests
Completed 10000 requests
Finished 10000 requests


Server Software:        nginx/1.1.19
Server Hostname:        10.6.2.213
Server Port:            80

Document Path:          /
Document Length:        151 bytes

Concurrency Level:      1000
Time taken for tests:   1.095 seconds
Complete requests:      10000
Failed requests:        0
Write errors:           0
Total transferred:      3620000 bytes
HTML transferred:       1510000 bytes
Requests per second:    9129.48 [#/sec] (mean)
Time per request:       109.535 [ms] (mean)
Time per request:       0.110 [ms] (mean, across all concurrent
requests)
Transfer rate:          3227.41 [Kbytes/sec] received

Connection Times (ms)
              min  mean[+/-sd] median   max
Connect:        0    9  11.4      2      34
Processing:     2   26  30.3     16     638
Waiting:        1   24  29.3     16     638
Total:          3   35  36.9     16     641

Percentage of the requests served within a certain time (ms)
  50%     16
  66%     31
  75%     53
  80%     56
  90%     67
  95%    109
  98%    164
  99%    178
 100%    641 (longest request)

# ./http_load -parallel 1000 -fetches 10000 ./htl.url
10000 fetches, 1000 max parallel, 1.51e+06 bytes, in 3.85493 seconds
151 mean bytes/connection
2594.08 fetches/sec, 391706 bytes/sec
msecs/connect: 211.437 mean, 3001.19 max, 0.102 min
msecs/first-response: 38.354 mean, 1456.25 max, 0.189 min
HTTP response codes:
  code 200 -- 10000

# weighttp -n 10000 -t 10 -c 1000 http://10.6.2.213
weighttp - a lightweight and simple webserver benchmarking tool

starting benchmark...
spawning thread #1: 100 concurrent requests, 1000 total requests
spawning thread #2: 100 concurrent requests, 1000 total requests
spawning thread #3: 100 concurrent requests, 1000 total requests
spawning thread #4: 100 concurrent requests, 1000 total requests
spawning thread #5: 100 concurrent requests, 1000 total requests
spawning thread #6: 100 concurrent requests, 1000 total requests
spawning thread #7: 100 concurrent requests, 1000 total requests
spawning thread #8: 100 concurrent requests, 1000 total requests
spawning thread #9: 100 concurrent requests, 1000 total requests
progress:  10% done
spawning thread #10: 100 concurrent requests, 1000 total requests
progress:  20% done
progress:  30% done
progress:  40% done
progress:  50% done
progress:  60% done
progress:  70% done
progress:  80% done
progress:  90% done
progress: 100% done

finished in 9 sec, 26 millisec and 801 microsec, 1107 req/s, 391
kbyte/s
requests: 10000 total, 10000 started, 10000 done, 10000 succeeded, 0
failed, 0 errored
status codes: 10000 2xx, 0 3xx, 0 4xx, 0 5xx
traffic: 3620000 bytes total, 2110000 bytes http, 1510000 bytes data

Posted at Nginx Forum: http://forum.nginx.org/read.php?2,225415,225415#msg-225415