This helps tons. speedguide.net has some registry 'tweeks' for different versions of windows. Also Win7 had the ability to turn on a FASTTCP type of congestion management called Compound TCP. I haven't tried the windows version so ymmv, but I have experienced great success by changing the congestion avoidance algorithm on other devices. -wil On Nov 25, 2010, at 4:19 PM, Adrian Chadd <adrian@creative.net.au> wrote:
TCP maximum window sizes.
Application socket buffer sizes.
Fix those and re-test!
Adrian
On Fri, Nov 26, 2010, Harris Hui wrote:
Hi
Does anyone have experience on design / implementing the Jumbo frame enabled network?
I am working on a project to better utilize a fiber link across east coast and west coast with the Juniper devices.
Based on the default TCP windows in Linux / Windows and the latency between east coast and west coast (~80ms) and the default MTU size 1500, the maximum throughput of a single TCP session is around ~3Mbps but it is too slow for us to backing-up the huge amount of data across 2 sites.
The following is the topology that we are using right now.
Host A NIC (MTU 9000) <--- GigLAN ---> (MTU 9216) Juniper EX4200 (MTU 9216) <---GigLAN ---> (MTU 9018) J-6350 cluster A (MTU 9018) <--- fiber link across site ---> (MTU 9018) J-6350 cluster B (MTU 9018) <--- GigLAN ---> (MTU 9216) Juniper EX4200 (MTU 9216) <---GigLAN ---> (MTU 9000) NIC - Host B
I was trying to test the connectivity from Host A to the J-6350 cluster A by using ICMP-Ping with size 8000 and DF bit set but it was failed to ping.
Does anyone have experience on it? please advise.
Thanks :-)
-- - Xenion - http://www.xenion.com.au/ - VPS Hosting - Commercial Squid Support - - $24/pm+GST entry-level VPSes w/ capped bandwidth charges available in WA -