[httperf] Server response hangs until timeout
martin.arlitt at hp.com
Wed Feb 15 08:28:29 PST 2012
I believe the issue is you need to explicitly add a '\n' at the end of your --add-header option. If you run httperf with the --print-request=header and --print-reply=header options, this may help you see if this is in fact the case.
From: httperf-bounces at linux.hpl.hp.com [mailto:httperf-bounces at linux.hpl.hp.com] On Behalf Of Galvin, Tom (HP Cloud Services)
Sent: Wednesday, February 15, 2012 4:03 AM
To: httperf at linux.hpl.hp.com
Subject: [httperf] Server response hangs until timeout
I am looking into using httperf to profile the Openstack API server.
I have been able to run httperf on an (over) simplified ping-pong example but run into problems hen a GET request is run against the API server itself.
httperf --server x.x.x.x --port=8774 --client=0/1 --uri
/v1.1/myproject/servers/detail?fresh=1329234243.33 --hog --method GET --add-header "X-Auth-Project-Id: myproject\nUser-Agent:
python-novaclient\nX-Auth-Token: XXXXXXXXXXX" --rate 1 --num-conns=1
--timeout=5 --num-calls=1 --recv-buffer=4096 --verbose
Tailing the logs I see the request gets processed by the server, but only after the timeout is breached.
Hence I get the reported Errors:
Errors: total 1 client-timo 1 socket-timo 0 connrefused 0 connreset 0
Similarly Wireshark shows the GET request immediately but the reply doesn't show until after the timeout.
Thanks for your help
httperf mailing list
httperf at linux.hpl.hp.com
More information about the httperf