Generic Server Solution for TCP/IP Tweaking

WELL WORTH READING!!!

Copy & Paste highlights from:


Disable TCP Auto-Tuning to Solve Slow Network

http://www.curuit.com/disable-tcp-a...ista--windows-7--windows-2008)-20070621145/

This is about an in-place "implement," for lack of a better word that tneds
to serve as some form of TCP/IP PERFORMANC suppression.

It's a small, relatively uninvasive fix that I've used myself. Albeit a small tweak, everything counts, right?

Below are the copy/pasted parts of said article.

Symptoms

That's what some of the clients experienced at different times:
Poor intermittent network performance
Slow network loading
Unable to open and load some websites or webpages using Internet Explorer or Firefox. The blue loading bar keeps running for a long time, but the pages fail to load.

Root cause

I have found that these problems might... (read article)

Solution

The solution (which can probably be viewed by some as a workaround) to the above problems is to disable the TCP/IP Auto-Tuning in Windows Vista, Windows 7, or Windows 2008.

The following are the solution implementation instructions:

Check the state or current setting of TCP Auto-Tuning
Open elevated command prompt with administrator

 

The symptoms definitely describe my crappy internet. Let me see if this fixes it

 

Please note that disabling Window auto-tuning will most probably affect the connection speed of other applications.

When Window auto-tuning is enabled, Windows changes the size of the Send/Receive-Window (that is, how many packets are sent before the other party has to acknowledge receiving them) according to network metrics like latency, packet loss, ...

A higher value usually leads to higher throughput (however if the Window size is too big, it's bad too.). By disabling auto-tuning, the Send/Receive Window is fixed at 8KB, which is usually too small for broadband connections and therefore giving you slower download/upload speed.

 

REALLY? I didn't know that... However, I never noticed any changes.

Any ideas/suggestions as to why I never noticed anything?

Thanks for mentioning.

 

I guess with the average 10-20 Mbit connections, you won't notice much of a change. You'd have to try downloading something from a source that could saturate your line easily and compare the results. The change would probably be small and also hard to notice since WAN connections rarely give you the same speed all the time.
You'd probably notice it with a 100 Mbit connection or with LAN traffic (especially if it's a 1 Gbit line).

Here are my results - first with receive window auto-tune enabled:

... and without:


I tried both settings three times, with auto-tuning off the speed was always at least 10 Mbit slower.

 

ZOMG! I have a true-blue gigabit connection myself, yes.

BTW: in reference to my post, it was suggested that I may need to recommend "ENABLE" it...

This is a new concept to me, that's why I wanted to put it up for discussion and not attempt to interpret the page, merely copy/paste.

******HAS ANYONE HAD NOTICABLE SUCCESSES W/THIS PROCESS?********

 

I'm sure those settings will improve pings for some people. I guess there are certain circumstances where the auto-tuning could probably affect latency in a bad way (e.g. when the connection is unstable and/or switches between high and really low throughput. The auto-tuning algorithm would probably have a hard time finding the best values, and since it's probably optimized for throughput, latency might suck. Disabling auto-tuning would lead to lowerthroughput, but the window size is fixed and that could lead to less jitter).
If your ping sucks, there's no harm in trying.

 

2 steps ahead, as always, Sycorax

I'm so glad you found this thread to contribute. Awesome.