Open gbjtv opened 9 years ago
Hi @gbjtv, communication between haproxy and the backend HTTP server doesn't involve wrk, does it? I'm not sure how anything wrk does could affect that part of the pipeline.
This is how I am able to replicate.
make TARGET=linux2628 USE_PCRE=1 USE_TFO=1 USE_OPENSSL=1 USE_ZLIB=1
mkdir -p /dev/shm/service/logs/
sudo /usr/sbin/nginx -c nginx.conf -p /dev/shm/service
base64 /dev/urandom | head -c 2048 > /dev/shm/service/2k
At this point I run ~/wrk/wrk -c 10 -d 10s -t 10
against
I experience the issue when running against port 9080-9082. wrk seems to hang after the first requests from each thread * connections.
Everything seems to work normally for port 9083 and 9084 which have the http-server-close option set.
I'm trying to use wrk to benchmark haproxy. I'm unable to get wrk to successfully run when http keepalives are enabled to backend servers (default behavior in haproxy 1.5) . I have to set "option http-server-close" in the backend section to get around this. Any ideas why wrk is failing when keepalives are enabled? It looks like each thread can make the first http request and get a response but stop sending any more requests.