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