TCP Tuning
LeslieCarr (Talk | contribs) |
LeslieCarr (Talk | contribs) |
||
| Line 13: | Line 13: | ||
initrwnd 10 | initrwnd 10 | ||
| − | This currently can only be set in 2.6.33 onwards (we are currently using 2.6.32 in our lucid distro). Recommend that we up this to 10 once we upgrade to Precise [[ http://en.wikipedia.org/wiki/Pangolin | + | This currently can only be set in 2.6.33 onwards (we are currently using 2.6.32 in our lucid distro). Recommend that we up this to 10 once we upgrade to Precise [[ [http://en.wikipedia.org/wiki/Pangolin Pangolin]Pangolin ]] |
:Can be set with the "ip route" command - any other way? | :Can be set with the "ip route" command - any other way? | ||
Revision as of 22:42, 27 January 2012
Suggestions
initcwnd 10 This makes the initial congestion window of 10, as tested by google. Default is 3. "Overall, more than 90% of client connections have a large enough receive window to fully benefit from using init cwnd=10 segments." Currently the only majorly used OS with a smaller advertised receive window is Linux 2.6.
- How do we implement this without just having an ip route command script on startup ?
tcp_fin_timeout 2 Lower our tcp_fin_timeout by 1 second. This matters if the other side does not respond to tcp_fin's. No need to keep this beyond 2 seconds as connections with an RTT > 2 seconds are basically dead anyways. Currently on our caches about 2-3% of all connections are stuck in the FIN state. 75% of them are in FIN_WAIT2 (Connection is closed, and the socket is waiting for a shutdown from the remote end.)
- can use puppet implemented files of sysctl.conf or look in puppet labs and use a module to implement.
initrwnd 10 This currently can only be set in 2.6.33 onwards (we are currently using 2.6.32 in our lucid distro). Recommend that we up this to 10 once we upgrade to Precise [[ PangolinPangolin ]]
- Can be set with the "ip route" command - any other way?
