martin.arlitt at hp.com
Tue Dec 13 09:53:01 PST 2011
According to the man page, --think-timeout is used from the start of the response; if the entire response is not received within the specified number of seconds, then the timer will expire and the transfer will be abandoned. The --think-timeout value is added to the --timeout value, which is used multiple times during the lifetime of the connection.
I'm not sure why you would want a timeout after the end of the response. If you have already received the entire content, what purpose will starting a timer serve?
If what you want to do is ensure a large object is transferred within N seconds, then you should be able to achieve that using a combination of --think-timeout and --timeout. You can collect a packet trace to confirm that it works as expected.
From: httperf-bounces at linux.hpl.hp.com [mailto:httperf-bounces at linux.hpl.hp.com] On Behalf Of Kurien Mathew
Sent: Tuesday, December 13, 2011 9:09 AM
To: httperf at linux.hpl.hp.com
Subject: [httperf] think-timeout
Given that the HTTP responses in my case could be large I would like a timeout on the end-of-response. Such a timeout will be triggered if the entire content does not arrive within the desired time. Is such a feature available?
>From the documentation, I read that --think-timeout is the time within which the reply must start arriving. This seems to be close to what I need but not exactly. And --timeout is not helpful either and it would trap slow connects. Is my understanding correct?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the httperf