EastCoasthandle
New Member
- Joined
- Apr 21, 2005
- Messages
- 6,885 (0.99/day)
System Name | MY PC |
---|---|
Processor | E8400 @ 3.80Ghz > Q9650 3.60Ghz |
Motherboard | Maximus Formula |
Cooling | D5, 7/16" ID Tubing, Maze4 with Fuzion CPU WB |
Memory | XMS 8500C5D @ 1066MHz |
Video Card(s) | HD 2900 XT 858/900 to 4870 to 5870 (Keep Vreg area clean) |
Storage | 2 |
Display(s) | 24" |
Case | P180 |
Audio Device(s) | X-fi Plantinum |
Power Supply | Silencer 750 |
Software | XP Pro SP3 to Windows 7 |
Benchmark Scores | This varies from one driver to another. |
Win7 Auto-tuning Feature
I've read some reports that Auto-tuning Feature in win7 is better then Vista. However, some still wish to disable this feature. I honestly don't know why one would do this as I'm not finding any real benefit for doing so.
source2
netsh interface tcp show global
This shows the status check or current setting of TCP Auto-Tuning
netsh interface tcp set global autotuninglevel=disabled
This will disable auto-tuning
netsh interface tcp set global autotuninglevel=normal
This will enable auto-tuning
netsh interface tcp set global autotuninglevel=highlyrestricted
This will set the autotuninglevel to "Allow the receive window to grow beyond its default value, but do so very conservatively".
I've read some reports that Auto-tuning Feature in win7 is better then Vista. However, some still wish to disable this feature. I honestly don't know why one would do this as I'm not finding any real benefit for doing so.
sourceWindows 7 and Vista include a "new & re-written" TCP stack that aims to take full advantage of hardware advances such as gigabit networking. Among the new features is Receive Window Auto-Tuning Level for TCP connections. TCP AutoTuning enables TCP window scaling by default and automatically tunes the TCP receive window size for each individual connection based on the bandwidth delay product (BDP) and the rate at which the application reads data from the connection, and no longer need to manually change TcpWindowSize registry key value which applies to all connection. Theoretically, with TCP auto-tuning, network connection throughput in should be improved for best performance and efficiency, without registry tweak or hack. However, this is not always the case, and may cause some Internet related issues and problems.
source2
netsh interface tcp show global
This shows the status check or current setting of TCP Auto-Tuning
netsh interface tcp set global autotuninglevel=disabled
This will disable auto-tuning
netsh interface tcp set global autotuninglevel=normal
This will enable auto-tuning
netsh interface tcp set global autotuninglevel=highlyrestricted
This will set the autotuninglevel to "Allow the receive window to grow beyond its default value, but do so very conservatively".
disabled: uses a fixed value for the tcp receive window. Limits it to 64KB (limited at 65535).
highlyrestricted: allows the receive window to grow beyond its default value, very conservatively
restricted: somewhat restricted growth of the tcp receive window beyond its default value
normal: default value, allows the receive window to grow to accommodate most conditions
experimental: allows the receive window to grow to accommodate extreme scenarios (not recommended, it can degrade performance in common scenarios, only intended for research purposes. It enables RWIN values of over 16 MB)
sourceNotes:
- Reportedly, some older residential NAT routers with a SPI firewall may have problems with enabled tcp auto-tuning in it's "normal" state, resulting in slow speeds, packet loss, reduced network performance in general.
- auto-tuning also causes problems with really old routers that do not support TCP Windows scaling. See MSKB 935400
- netsh set commands take effect immediately after executing, there is no need to reboot.
- sometimes when using "normal" mode and long lasting connections (p2p software / torrents), tcp windows can get very large and consume too much resources, if you're experiencing problems try a more conservative (restricted) setting.
Last edited: