search

yubin00145865 / iperf

Automatically exported from code.google.com/p/iperf
Other
0 stars 0 forks source link

report CPU utilization for both sender and receiver in output #30

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
It can often be helpful to know the average CPU utilization for both the 
sending and receiving hosts during an iperf, to determine if one side is 
CPU-bound.

As an example, nuttcp reports CPU utilization on the summary line at the end of 
a transfer, e.g. "%TX" and "%RX" in the output below:

70908.4355 MB /  60.06 sec = 9903.3007 Mbps 19 %TX 43 %RX 0 retrans 0.10 
msRTT

(Of course, when you run nuttcp in UDP mode, it is expected that the TX side 
will go to 100%...)

Original issue reported on code.google.com by chris.t....@gmail.com on 24 Aug 2010 at 6:21

GoogleCodeExporter commented 8 years ago 
As a side note, I have run into cases where bad performance reported by a perf 
test application was due to other process(es) on the host consuming all of the 
CPU.  I was once diagnosing performance problems between hosts that were 
streaming video, and after a lot of testing, found that some process had lots 
its mind and was eating up all of the CPU, causing all sorts of problems.  
Simply reporting the average CPU during the test would allow users to know 
whether their host simply isn't fast enough, or is spending all of its time 
doing something else...

Original comment by chris.t....@gmail.com on 24 Aug 2010 at 6:26

GoogleCodeExporter commented 8 years ago

Original comment by bltier...@gmail.com on 7 Sep 2012 at 1:16

GoogleCodeExporter commented 8 years ago 
I think this is a great idea.  How hard is this to do portably in a multicore 
world?  ;)

Original comment by jdu...@es.net on 10 Sep 2012 at 4:28

GoogleCodeExporter commented 8 years ago 
The local & remote CPU utilization is recorded, and does get shown if the 
-V/--verbose flag is specified.  Looks like this:

Host CPU Utilization: 99.8%
Remote CPU Utilization: 16.6%

Should I change it to show up by default, instead of only in verbose mode?  If 
not, then I guess this issue is Done.

Original comment by jef.posk...@gmail.com on 3 Nov 2012 at 6:07

GoogleCodeExporter commented 8 years ago

Original comment by bltier...@es.net on 25 Feb 2013 at 11:10