arlitt at hpl.hp.com
Tue Jan 10 13:25:31 PST 2006
If I remember correctly for a timeout value of N, you have:
N seconds to complete the TCP SYN handshake to establish the connection;
N seconds to issue the request;
N seconds to receive the first byte of the response from the server;
N seconds to receive the last byte of the response from the server.
in your case, is httperf timing out the connection 10 seconds after the
initial HTTP response packet is received? if so, this is normal httperf
behavior (i.e., it does not reset the timer on each packet arrival from
the server). this emulates the way users can abort a request/connection
if they feel it is taking too long, even though it may be making progress
On Tue, 10 Jan 2006, Mark Pors wrote:
> I have a question about the --timeout parameter.
> When doing this: httperf --server=athens.pm.org --uri=/big --timeout=10
> The file 'big' is about 7MB large.
> The operation times out after a bit more than 10 seconds, which is very
> different from what a browser does.
> I was looking at the bandwidth of the connection, and there was data
> coming and going during these 10 seconds
> Is this the normal expected httperf behavior?
> I would expect the timeout to be reset when the server responds at a
> specific point?
> The man page is not very clear on this, please help me out on this.
> Pors BV
> Internet Projects
> httperf mailing list
> httperf at linux.hpl.hp.com
More information about the httperf