Excerpts from martin's message of Mon Nov 15 05:30:11 -0600 2010: > Me and a friend of mine troubleshooted one issue with TCP throughput > and used "TCP window size flag" option of Iperf. The problem was, that > Iperf often ignored this flag. For example like this: > > TCP window size: 16 KByte (WARNING: requested 150 KByte) > > However, I tested now between a FreeBSD, Ubuntu and Suse machine using > Iperf versions 2.0.4 and 2.0.5 and now it seemed to be working. Have > you encountered any issues with "TCP window size flag"? Should TCP > window size be configured only at client side or server side as well? > > thanks you in advance! >
This looks like the OS had a limit on how large of a window you could request. This isn't a bug with Iperf but an OS imposed limit. For information on how to raise this limit. http://fasterdata.es.net/TCP-tuning/background.html There are links on that page for details on tuning TCP on a variety of operating systems. Jon -- Jon M. Dugan <jdu...@es.net> ESnet Network Engineering Group Lawrence Berkeley National Laboratory ------------------------------------------------------------------------------ Increase Visibility of Your 3D Game App & Earn a Chance To Win $500! Tap into the largest installed PC base & get more eyes on your game by optimizing for Intel(R) Graphics Technology. Get started today with the Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs. http://p.sf.net/sfu/intelisp-dev2dev _______________________________________________ Iperf-users mailing list Iperf-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/iperf-users
