Hi,
What you pointed out below is true. But I am more
interested in the relative performance since the number
I measured were under exactly the same setup and traffic
condition. I am just curious why IPComp was _relatively_
(and signigicantly) slower than most of the encryption
algorithm. So I guess bandwidth is probably not the best
pointer since what I end up comparing was really the
implementations of different encryption/compression
algorithms which are CPU-bound in this case.
regards,
yushun.
> AFAIK, netperf TCP_STREAM test (and may be others) is extremely
> susceptible to network delays. For example, for a fast Ethernet
> connection with, say, 30msec packet delay, netperf may show less than
> 10Mbits/sec bandwidth instead of the usual 90+Mbits/sec. Clearly,
> bandwidth and response times are orthogonal measurements, but netperf
> design ties them together.
>
> Depending on your test environment and purposes, netperf throughput
> results may be very misleading.
>
> $0.02,
>
> Alex.
>
>
>
>
>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-net" in the body of the message
