[httperf] Why does httperf take extra time even after completion
arlitt at hpl.hp.com
Tue Jul 4 06:58:49 PDT 2006
without knowing anything about the test you were running, or about the
configuration of the client, it is difficult to know what was happening.
I expect that your test did not run cleanly in some way; e.g., some
connections failed, or httperf had trouble getting file descriptors at
some point during the test. However, without knowing more about the test
or the httperf output from the test this is just speculation.
On Tue, 4 Jul 2006, Prakhar Goyal wrote:
> Hello Sir,
> The tool proved to be very helpful to me in my performance analysis of Web
> In one expt, it displayed a test duration of 406 secs.
> I ran 'top' and 'sar' on the web server, and also on the client machine,
> on which httperf was running.
> I found that when the web server has stopped utilizing cpu (ie, the test
> is completed) , then also the httperf was running for some 6 -8 secs with
> cpu util of 100 % on the client machine.
> Why does httperf take extra time ( in this case 6-8 secs) , even after the
> web server has stopped handling the requests..
> Any kind of help will be most valauble.
> IIT Bombay, India.
> Prakhar Goyal
> Computer Science & Engineering Dept.
> IIT Bombay.
> Homepage: http://www.cse.iitb.ac.in/~prakhargoyal
> httperf mailing list
> httperf at linux.hpl.hp.com
More information about the httperf