3 ms·

something like "wrk -d 10 -c 1000 -t 4 http://127.0.0.1/byte.txt http://127.0.0.1/byte.txt (one byte file) did: Requests/sec: 100.00 Transfer/sec: 11.91

• nXqd 11y ago
  this is really really fast.
  • edsiper2 11y ago
    are u kidding ? expectation is no less than a 100k req/s.
• trentnelson 11y ago
  Doesn't look like it supports HTTP pipelining: [trent@ubuntu/ttypts/4(~s/wrk)%] ./wrk -c 1 -t 1 --latency -d 5 http://localhost:8080/Makefile Running 5s test @ http://localhost:8080/Makefile 1 threads and 1 connections Thread Stats Avg Stdev Max +/- Stdev Latency 35.00us 0.00us 35.00us 100.00% Req/Sec 10.00 0.00 10.00 100.00% Latency Distribution 50% 35.00us 75% 35.00us 90% 35.00us 99% 35.00us 1 requests in 5.10s, 1.57KB read Requests/sec: 0.20 Transfer/sec: 314.55B Note the 1 request. For 1000 clients, it's only doing 1000 requests: [trent@ubuntu/ttypts/4(~s/wrk)%] ./wrk -c 1000 -t 1 --latency -d 5 http://localhost:8080/Makefile Running 5s test @ http://localhost:8080/Makefile 1 threads and 1000 connections Thread Stats Avg Stdev Max +/- Stdev Latency 307.93ms 552.88ms 1.63s 87.10% Req/Sec 414.29 439.07 1.34k 85.71% Latency Distribution 50% 4.11ms 75% 407.63ms 90% 1.63s 99% 1.63s 1000 requests in 5.01s, 1.53MB read Socket errors: connect 0, read 41, write 0, timeout 0 Requests/sec: 199.79 Transfer/sec: 312.96KB