Okay cool. I hope they didn't set a fixed buffer size. I will download iperf2 and try it out. I'll let you know how if there are any issues. BTW: Do you know who is responsible for iperf3? That's the tool that I have been getting limited bandwidth reports on.
On Tue, Feb 4, 2020 at 2:23 PM Bob McMahon <bob.mcma...@broadcom.com> wrote: > I just checked with our windows engineer and he said the iperf 2 > <https://sourceforge.net/projects/iperf2/>team no longer uses cygwin but > rather builds a native version. > > Bob > > On Tue, Feb 4, 2020 at 2:07 PM Daniel Havey <dha...@gmail.com> wrote: > >> Hi, I'm Daniel Havey from Microsoft Windows. I'm the PM for transports >> (TCP/QUIC) and there is a bug in the cygwin1.dll that was distributed with >> the iperf binaries. The bug limits maximum bandwidth achievable by the >> iperf tool. Details can be found in my blogpost: >> https://techcommunity.microsoft.com/t5/networking-blog/windows-network-performance-suffering-from-bad-buffering/ba-p/339668 >> >> We worked with RedHat on Cygwin to fix the bug, but I am still getting >> reports of limited bandwidth from windows iperf users. The fix is simple. >> Just download the new cygwin1.dll from the cygwin website and the problem >> will be fixed. >> >> thanks ;) >> ...Daniel >> _______________________________________________ >> Iperf-users mailing list >> Iperf-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/iperf-users >> >
_______________________________________________ Iperf-users mailing list Iperf-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/iperf-users
