Quote:
Quote:
Then try toggling the value of /proc/sys/net/ipv4/tcp_window_scaling
(eg. just do echo 0 > /proc/sys/net/ipv4/tcp_window_scaling).


Initially it was 1, set it to 0, and the speeds went to what was expected on the next attempt. Looks like it only works for new connections, won't change existing ones. No big deal though since we can just toss this in a startup script and be done with it.

Thank you so much for the help. The only reason I got involved was because this issue had been going on long enough to now impact my development schedule for this part of the scrum. Now I can get back to my development tasks.


Peachy. A better solution, than simply disabling it, is to try the other fix of setting the tcp_rmem numbers back to their pre-2.6.17 values. The numbers I posted earlier should work, but if not, try reducing the last number by half (powers of two) until it does work.

This will give the best throughput.

Cheers


Edited by mlord (10/05/2007 15:01)