Re: [tcpm] [Tmrg] Increasing the Initial Window - Notes

Jerry Chu <hkchu@google.com> Wed, 17 November 2010 19:28 UTC

Return-Path: <hkchu@google.com>
X-Original-To: tcpm@core3.amsl.com
Delivered-To: tcpm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 86B033A6989 for <tcpm@core3.amsl.com>; Wed, 17 Nov 2010 11:28:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.725
X-Spam-Level:
X-Spam-Status: No, score=-105.725 tagged_above=-999 required=5 tests=[AWL=0.251, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sLKFO8VRxlU6 for <tcpm@core3.amsl.com>; Wed, 17 Nov 2010 11:28:11 -0800 (PST)
Received: from smtp-out.google.com (smtp-out.google.com [216.239.44.51]) by core3.amsl.com (Postfix) with ESMTP id CEF653A698E for <tcpm@ietf.org>; Wed, 17 Nov 2010 11:27:46 -0800 (PST)
Received: from kpbe15.cbf.corp.google.com (kpbe15.cbf.corp.google.com [172.25.105.79]) by smtp-out.google.com with ESMTP id oAHJRpX9030060 for <tcpm@ietf.org>; Wed, 17 Nov 2010 11:27:51 -0800
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1290022071; bh=JoA0y03aIIHqbhLmYQ6s19I8EL4=; h=MIME-Version:In-Reply-To:References:Date:Message-ID:Subject:From: To:Cc:Content-Type; b=N6t73liA26+xvKoV8Z3s0KL3BnOIOg2OBNBd+OJg6TnkOh2uJ3d4MR13WJNI0oT/K BEjMwQqChsRb6EPloBuKw==
Received: from yxg6 (yxg6.prod.google.com [10.190.2.134]) by kpbe15.cbf.corp.google.com with ESMTP id oAHJP5dm009435 for <tcpm@ietf.org>; Wed, 17 Nov 2010 11:27:50 -0800
Received: by yxg6 with SMTP id 6so1716566yxg.26 for <tcpm@ietf.org>; Wed, 17 Nov 2010 11:27:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=beta; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=GnnRU9Uy8G2Iptza3gUTnuIrxezyf+02As3WBVXrsGc=; b=UQ7VBwHn2tm4bwHotJpgiHp/JIoBu/SiwQHfcx2elpB127p4oJUPWWz51pa4CzeUPU 32lkNo98aFhYP9HrIMww==
DomainKey-Signature: a=rsa-sha1; c=nofws; d=google.com; s=beta; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=uob5nu3rQhIIxud/t3DI5Z1oQ38mLcY0OQiQ/vytQMidv3k/TfIfzE+ElFuWmgOPa8 tFHpcchthHHkSYSA09+Q==
MIME-Version: 1.0
Received: by 10.150.228.16 with SMTP id a16mr14606886ybh.177.1290022069555; Wed, 17 Nov 2010 11:27:49 -0800 (PST)
Received: by 10.151.158.13 with HTTP; Wed, 17 Nov 2010 11:27:49 -0800 (PST)
In-Reply-To: <AD2BFE84-CA5B-4CDC-8822-1FC2713E3AE0@cisco.com>
References: <20101110152857.GA5094@hell> <804D02FE-39AF-4437-BB15-C2247842E120@mac.com> <20101110170017.GF5094@hell> <97C75EA8-6CC7-444C-A19D-370148B81918@mac.com> <20101110174056.GH5094@hell> <AANLkTim7g=XqfSMHpHVbw1qqPOL-oNApt2i_2RCt0SCi@mail.gmail.com> <AD2BFE84-CA5B-4CDC-8822-1FC2713E3AE0@cisco.com>
Date: Wed, 17 Nov 2010 11:27:49 -0800
Message-ID: <AANLkTin1wGme1DUERiH6At_1NSOQwPtYeEN1OdRO7UP2@mail.gmail.com>
From: Jerry Chu <hkchu@google.com>
To: Fred Baker <fred@cisco.com>
Content-Type: multipart/alternative; boundary="000e0cd47d9635575c049544ab65"
X-System-Of-Record: true
Cc: tcpm <tcpm@ietf.org>, tmrg <tmrg-interest@icsi.berkeley.edu>
Subject: Re: [tcpm] [Tmrg] Increasing the Initial Window - Notes
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcpm>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Nov 2010 19:28:36 -0000

On Mon, Nov 15, 2010 at 8:07 PM, Fred Baker <fred@cisco.com> wrote:

>
> On Nov 11, 2010, at 7:48 AM, Jerry Chu wrote:
>
> > I wonder what factors will argue that the initial quantum can't be
> changed?
> > Someone has argued in the past IW10 effectively "disable CC algorithm".
> > But haven't we already done that years ago when moving up IW from 1 to 3
> if
> > one insisted then that the initial quantum must be 1?
>
> Actually, no. I may be the person who said that this effectively disables
> congestion control in the average case; my reason for saying that is that
> per what little data I have, the average TCP transfer is on the order of 15K
> bytes, which is about ten 1460 byte segments.
>
> Now, the median is much smaller - on the order of two or three data
> segments each direction, which is where you get your comment. But the fact
> that browsers, Bittorrent, and other applications open multiple sessions
> simultaneously argues that a given endpoint having multiple packets in
> flight simultaneously doesn't hurt, and research done at the time by Mark
> Allman and others showed that IW=2..4 wasn't a problem and did in fact
> reduce the median session to a single RTT for data. But the median session
> doesn't create a congestion problem.
>
> The question I have been asking is how IW=10 affects parallel sessions on
> relatively low speed links. My sense is that the sudden arrival of O(15K)
> bytes at a 56 KBPS line, which is to say the insertion of a tad over two
> seconds delay in all competing sessions plus an increase in their
> probability of loss, is likely to cause them all to be disrupted. You told
> me verbally that in your tests it is net beneficial to the parallel
> sessions, but in thought experiments I'm not sure how that can be true; I'd
> be


Perhaps you've missed something in your thought process? In addition to some
points
Ilpo has made in his reply, another plausible explanation that you may not
have
considered is that for the same amount of data to be transfered, IW10 is
simply more
"efficient" in average than IW3. It is true that IW10 causes a larger burst
to be sent,
but it is not like you're going to get the same frequency of 10-pkt bursts
as compared
to 3-pkt bursts. The comparison is more like a single large burst vs three
smaller
bursts. It's not clear to me one can actually prove the single large burst
will often
cause more damage to competing flows than 3 smaller bursts and our testbed
sorta
confirmed this.

Jerry


> fascinated to see the data that shows that competing voice/video sees no
> frame loss or induced noise, that competing file transfers slow down but do
> not see redundant retransmissions, and so on.
>
> So, IW=2..4 demonstrably works pretty well everywhere, but IW=10 seems to
> me only sensible on MPBS and GBPS, not KBPS, scale links.