Vista Automatic RWIN

[kinko]

Hello,

I've noticed when using Vista to do speed tests on my home connection, the speed "accelerates." I believe this is a part of the new network stack. If the rwin settings are switched from automatic to static (off) the speed appears instant. ( Howto: http://www.dslreports.com/faq/15525 ) I was wondering what the real use results are from using vista (auto rwin), vista (static rwin) or xp (static) for browsing with Rev A or something that wouldn't necessarily max the connection. Really, the issue is the frequency of the auto-adjustment and the changing nature of a rev A conncetion (all kinds of RFI) and the effects it has on efficiency.

Thanks.

[kinko]

This is vista x64 from a titan with Rev A rom, 2-3 bars and 1200/200 on a speed test

Ping with Autotuning:

Pinging google.com [64.233.187.99] with 32 bytes of data:

Reply from 64.233.187.99: bytes=32 time=121ms TTL=240
Reply from 64.233.187.99: bytes=32 time=135ms TTL=240
Reply from 64.233.187.99: bytes=32 time=123ms TTL=240
Reply from 64.233.187.99: bytes=32 time=119ms TTL=240
Request timed out.
Reply from 64.233.187.99: bytes=32 time=148ms TTL=240
Reply from 64.233.187.99: bytes=32 time=124ms TTL=240
Reply from 64.233.187.99: bytes=32 time=148ms TTL=240
Reply from 64.233.187.99: bytes=32 time=138ms TTL=240
Reply from 64.233.187.99: bytes=32 time=127ms TTL=240
Reply from 64.233.187.99: bytes=32 time=266ms TTL=240
Reply from 64.233.187.99: bytes=32 time=123ms TTL=240
Reply from 64.233.187.99: bytes=32 time=144ms TTL=240
Reply from 64.233.187.99: bytes=32 time=124ms TTL=240
Reply from 64.233.187.99: bytes=32 time=151ms TTL=240
Request timed out.
Reply from 64.233.187.99: bytes=32 time=175ms TTL=240
Reply from 64.233.187.99: bytes=32 time=152ms TTL=240

Ping statistics for 64.233.187.99:
Packets: Sent = 18, Received = 16, Lost = 2 (11% loss),
Approximate round trip times in milli-seconds:
Minimum = 119ms, Maximum = 266ms, Average = 144ms


Ping without autotuning:
Pinging google.com [64.233.187.99] with 32 bytes of data:

Reply from 64.233.187.99: bytes=32 time=143ms TTL=240
Reply from 64.233.187.99: bytes=32 time=126ms TTL=240
Reply from 64.233.187.99: bytes=32 time=129ms TTL=240
Reply from 64.233.187.99: bytes=32 time=154ms TTL=240
Reply from 64.233.187.99: bytes=32 time=132ms TTL=240
Reply from 64.233.187.99: bytes=32 time=129ms TTL=240
Reply from 64.233.187.99: bytes=32 time=122ms TTL=240
Reply from 64.233.187.99: bytes=32 time=208ms TTL=240
Reply from 64.233.187.99: bytes=32 time=136ms TTL=240
Reply from 64.233.187.99: bytes=32 time=141ms TTL=240
Reply from 64.233.187.99: bytes=32 time=145ms TTL=240
Reply from 64.233.187.99: bytes=32 time=127ms TTL=240
Reply from 64.233.187.99: bytes=32 time=782ms TTL=240
Reply from 64.233.187.99: bytes=32 time=117ms TTL=240
Reply from 64.233.187.99: bytes=32 time=143ms TTL=240
Reply from 64.233.187.99: bytes=32 time=147ms TTL=240
Reply from 64.233.187.99: bytes=32 time=119ms TTL=240
Reply from 64.233.187.99: bytes=32 time=196ms TTL=240

Ping statistics for 64.233.187.99:
Packets: Sent = 18, Received = 18, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 117ms, Maximum = 782ms, Average = 177ms