jamal wrote:
On Fri, 2007-08-06 at 10:27 -0700, Rick Jones wrote:
[..]
you cannot take the netperf service demand directly - each netperf is
calculating assuming that it is the only thing running on the system.
It then ass-u-me-s that the CPU util it measured was all for its work.
This means the service demand figure will be quite higher than it really is.
So, for aggregate tests using netperf2, one has to calculate service
demand by hand. Sum the throughput as KB/s, convert the CPU util and
number of CPUs to a microseconds of CPU consumed per second and divide
to get microseconds per KB for the aggregate.
From what you are saying above seems to me that for more than one proc
it is safe to just run netperf4 instead of netperf2?
Well, it is easier to be safe on aggregates with netperf4 than netperf2
although at present it is more difficult to run netperf4 than netperf2
It also seems reasonable to set up large socket buffers on the receiver.
For bulk transfers I often do.
rick
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
