Re: Iperf Issues.
Craig,
First I would suggest visiting some of the tuning sites listed on the
Iperf page to set-up some OS specific parameters. Next I would look at any
QOS Packet Schedulers in the properties of your network interfaces. This
fine feature removes 10% or more bandwidth to be used by QOS apps which
you probably are not be running. I have no idea what MS has changed
between the service packs that would affect performance unless they
changed the tuning parameters listed on the tuning sites mentioned above.
I know from experience that you should be able to get much closer to line
level speeds with the 2k or newer window.
Good luck,
Kevin
On Thu, 25 Sep 2003, Mitch Kutzko wrote:
> >From: Craig Marshall <Craig.Marshall --at-- ospreynet.co.uk>
> >To: "'dast --at-- nlanr.net'" <dast --at-- nlanr.net>
> >Subject: Iperf Issues.
> >Date: Thu, 25 Sep 2003 11:23:57 +0100
> >
> >Can you tell me if there are any issues with using IPERF on different
> >Service Pack levels of Windows 2000?
> >
> >I have 2 Servers which I am testing a Gigabit Ethernet switch. One server is
> >Running service Pack 2, and one is running Service Pack 3.
> >
> >I run the IPERF server on the SP2 box with the following command: iperf -s
> >-u -i 1
> >Then run the client from the SP3 box with the following command: iperf -c
> ><ip address> -b 1000m -w 128k
> >The bandwidth that is reported as around 50MB
> >
> >When I run the test the opposite way around (with the SP3 box as the server)
> >the bandwidth is reported as upwards of 200MB.
> >
> >I'm running IPERF v 1.7.0
> >
> >Thanks
> >
> >Craig Marshall
> >Osprey Network & Communications
> >Suit 4, Tower House
> >High Street
> >Aylesbury
> >Buckinghamshire
> >HP20 1SQ
> >Tel: +44 7880746645
> >Email craig.marshall --at-- ospreynet.co.uk