nanog mailing list archives

RE: 10gig coast to coast


From: James Braunegg <james.braunegg () micron21 com>
Date: Tue, 18 Jun 2013 15:53:48 +0000

Dear All

We Deal with TCP window size all day every day across the southern cross from LA to Australia which adds around 
160ms...  I've given up looking for a solution to get around physical physics of sending TCP traffic a long distance at 
a high speed....

UDP traffic however comes in very fast....

Kindest Regards

James Braunegg
W:  1300 769 972  |  M:  0488 997 207 |  D:  (03) 9751 7616
E:   james.braunegg () micron21 com  |  ABN:  12 109 977 666   



This message is intended for the addressee named above. It may contain privileged or confidential information. If you 
are not the intended recipient of this message you must not use, copy, distribute or disclose it to anyone other than 
the addressee. If you have received this message in error please return the message to the sender by replying to it and 
then delete the message from your computer.


-----Original Message-----
From: Phil Fagan [mailto:philfagan () gmail com] 
Sent: Wednesday, June 19, 2013 12:16 AM
To: Jakob Heitz
Cc: <nanog () nanog org>
Subject: Re: 10gig coast to coast

Sorry; yes Sawtooth is the more accurate term. I see this on a daily occurance with large data-set transfers; generally 
if the data-set is large multiples of the initial window. I've never tested medium latency(
<100ms) with small enough payloads where it may pay-off threading out many thousands of sessions. However, medium 
latency with large files (50M-10G) threads well in the sub 200 range and does a pretty good job at filling several Gig 
links. None of this is scientific; just my observations from the wild.....infulenced by end to end tunings per 
environment.




On Tue, Jun 18, 2013 at 7:45 AM, Jakob Heitz <jakob.heitz () ericsson com>wrote:

Thanks Fred. Sawtooth is more familiar.
How much of that do you actually see in practice?

Cheers,
Jakob.


On Jun 18, 2013, at 6:27 AM, "Fred Reimer" <freimer () freimer org> wrote:

It is also called a "sawtooth" or similar terms.  Just google "tcp 
sawtooth" and you will see many references, and images that depict 
the traffic pattern.

HTH,

Fred Reimer | Secure Network Solutions Architect Presidio | 
www.presidio.com <http://www.presidio.com/>
3250 W. Commercial Blvd Suite 360, Oakland Park, FL 33309
D: 954.703.1490 | C: 954.298.1697 | F: 407.284.6681 |
freimer () presidio com
CCIE 23812, CISSP 107125, HP MASE, TPCSE 2265




On 6/18/13 9:20 AM, "Jakob Heitz" <jakob.heitz () ericsson com> wrote:

Date: Mon, 17 Jun 2013 22:04:52 -0600
From: Phil Fagan <philfagan () gmail com> ... you could always thread 
the crap out of whatever it is your transactioning across the link 
to make up for TCP's jackknifes...

What is a TCP jackknife?

Cheers.
Jakob.






--
Phil Fagan
Denver, CO
970-480-7618

Current thread: