security writes:
> The down side is that the best speed I got was around 362Mbps on a
> gigE link (with netpipe). I had hoped for better.
362Mb/s is way too low for 1GbE.
You might want to try a UDP test to isolate the bottleneck somewhat.
Try netperf -tUDP_STREAM -Hmacpro02-m -- -m 1472
At Wed, 30 May 2007 13:49:43 -0700,
security wrote:
> Drew,
> Odd you should mention netperf. It yielded nearly identical
> asymmetric results as iperf. I ended up testing with netpipe (NPtcp).
> It reported fairly symmetric speeds between the two boxes when the send
> and recv buffers were s
> security writes:
> > Sent this to -net and didn't get much info, so I'll try here since
> > there's some overlap
> >
> > Summary: Using iperf to measure TCP net speed between a linux (kubuntu
> edgy) and
>
> Iperf is probably your problem, it tends to perform really poorly on
> nearly any
security writes:
> Sent this to -net and didn't get much info, so I'll try here since
> there's some overlap
>
> Summary: Using iperf to measure TCP net speed between a linux (kubuntu
> edgy) and
Iperf is probably your problem, it tends to perform really poorly on
nearly any OS other than
Thanks Steve. Just tried it and no change. I also rebuilt my kernel
for polling and set it on the em0 device. While it did lower interrupt
time, it didn't make any real change in my numbers
jim
Steven Hartland wrote:
> You might want to try setting:
> net.inet.tcp.inflight.enable=0
>
> Just c
You might want to try setting:
net.inet.tcp.inflight.enable=0
Just changing this on our FreeBSD 6.2 boxes enabled them to achieve
full line rate with ftp / proftpd transfers.
Steve
- Original Message -
From: "security" <[EMAIL PROTECTED]>
Switch is the Netgear GS105 (5 port, supp
Sent this to -net and didn't get much info, so I'll try here since
there's some overlap
Summary: Using iperf to measure TCP net speed between a linux (kubuntu edgy)
and
freebsd box over gigE, I see significant speed difference depending on
the data direction. Pushing data from the freebsd box t
