On Mon, 5 Feb 2001, Rick Jones wrote:
> > Netperf ties response time and throughput and, hence, cannot show
> > meaningful throughput measurements in environments with packet delays.
> Huh? Are you refering to the synchronous nature of the netperf TCP_RR
> test? If so, then it was _inteneded_ to show the delay and was not
> intended as a throughput measurement.
I was actually talking about the [default] TCP_STREAM test.
I had no intention to somehow pummel the test or the netperf tool
itself! I was just pointing out that the default TCP_STREAM test will
not show real raw throughput on a link with packet delays.
For example, TCP_STREAM reports ~1.6Mbit/sec throughput with PolyMix-3
server-side delays (40msec in each direction) and a 100Mbit link. The
actual throughput (e.g., a throughput that an HTTP client may see) is
If there are more appropriate netperf tests/parameters that should be
used in an environment with delays, please let me know! The defaults
were sufficient for our limited tests, but we are always happy to
improve the methodology.
This archive was generated by hypermail 2b29 : Tue Jul 10 2001 - 12:00:17 MDT