[105125] in North American Network Operators' Group
RE: Best utilizing fat long pipes and large file transfer
daemon@ATHENA.MIT.EDU (Lincoln Dale)
Thu Jun 12 21:00:42 2008
From: "Lincoln Dale" <ltd@interlink.com.au>
To: "'Sean Knox'" <sean@craigslist.org>, <nanog@merit.edu>
Date: Fri, 13 Jun 2008 10:58:46 +1000
In-Reply-To: <4851A53B.4010400@craigslist.org>
Errors-To: nanog-bounces@nanog.org
> I'm looking for input on the best practices for sending large files over
> a long fat pipe between facilities (gigabit private circuit, ~20ms RTT).
providing you have RFC1323 type extensions enabled on a semi-decent OS, a 4MB
TCP window should be more than sufficient to fill a GbE pipe over 30msec.
with a modified TCP stack, that uses TCP window sizes up to 32MB, i've worked
with numerous customers to achieve wire-rate GbE async replication for
storage-arrays with FCIP.
the modifications to TCP were mostly to adjust how it reacts to packet loss,
e.g. don't "halve the window".
the intent of those modifications is that it doesn't use the "greater internet"
but is more suited for private connections within an enterprise customer
environment.
that is used in production today on many Cisco MDS 9xxx FC switch environments.
> I'd like to avoid modifying TCP windows and options on end hosts where
> possible (I have a lot of them). I've seen products that work as
> "transfer stations" using "reliable UDP" to get around the windowing
> problem.
given you don't want to modify all your hosts, you could 'proxy' said TCP
connections via 'socat' or 'netcat++'.
cheers,
lincoln.
