[httperf] Maximum connect burst length
TTerrill at synacor.com
Fri Nov 30 06:22:14 PST 2012
My understanding is this:
1. Httperf attempts to send requests in a uniform distribution across every second. So if you ask for 10,000 connections/sec, it will initiate a request every 1/10,000th of a second. It will continue making requests in the subsequent seconds irregardless of it got replies to the previous ones.
2. Httperf does not "assume a request has completed" or "clean up sockets" at the system level. The OS reuses (cleans up) socket after the TIME_WAIT period has elapsed once the connection has been closed (either due to a reply, or timeout).
I have never used the maximum connection burst length, so I'm not sure how it plays into this.
Hopefully this helps (and hopefully I'm right! :o)
From: Vikash Kumar <vikash.kumar at oneconvergence.com<mailto:vikash.kumar at oneconvergence.com>>
Date: Friday, November 30, 2012 2:24 AM
To: "httperf at linux.hpl.hp.com<mailto:httperf at linux.hpl.hp.com>" <httperf at linux.hpl.hp.com<mailto:httperf at linux.hpl.hp.com>>
Subject: [httperf] Maximum connect burst length
Httperf o/p gives :
Maximum connect burst length
Can anyone please explain about this?
What exactly it refers to?
Is this burst length is in millisecond or seconds?
How can we get connection rate and request rate from this number?
Some important question:
Let us suppose, we fix our connection rate to 10000 conn/sec, then how does the httperf generate 10000 req/sec? Are all these requests are made parallely ? Is this has anything to do with the burst length as we get at output?
How does httperf assume that a request has completed and how does it clean up the sockets in use?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the httperf