| |||||||||||||
Increasing the TCP initial congestion windowIncreasing the TCP initial congestion windowPosted Feb 10, 2011 3:59 UTC (Thu) by butlerm (subscriber, #13312)Parent article: Increasing the TCP initial congestion window There are a couple of other things that should be done: First, the minimum retry time out should be reduced to approximately 1 ms, or whatever the timer accuracy allows. On local area networks a MIN_RTO of 1 second is ridiculous. Second, the syn retry timeout should be reduced from 1 second to 200 ms or so. The only reason to have it so high is if the bottleneck link is a 56 kbps modem or something. It would be great if there were route attributes that allow these numbers (or something that allows them to be derived) to be further customized on a route specific basis. In particular to increase them on the default route in the case of a unusually slow link, and to decrease them for the route to the local LAN.
(Log in to post comments)
Increasing the TCP initial congestion window Posted Feb 14, 2011 3:23 UTC (Mon) by ivannovick (guest, #72897) [Link]
Are you talking about TCP_RTO_MIN? I seem to believe this is hard coded in the kernel to 200 Milliseconds. Under the workload I have tested, huge gains were had by just changing this value to 10 miliseconds.
It would be great if this was configurable or lowered ... as the 200 miliseconds seems to cause a real bottleneck in some cases.
Does anyone know if this has been proposed or is being made configurable?
Cheers,
|
|||||||||||||