Re: [tcpm] Increasing the Initial Window - Notes

Jerry Chu <hkchu@google.com> Mon, 15 November 2010 08:02 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 015A63A6C68 for <tcpm@core3.amsl.com>; Mon, 15 Nov 2010 00:02:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.6
X-Spam-Level:
X-Spam-Status: No, score=-105.6 tagged_above=-999 required=5 tests=[AWL=0.377, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 Mnobljj0MEmD for <tcpm@core3.amsl.com>; Mon, 15 Nov 2010 00:02:46 -0800 (PST)
Received: from smtp-out.google.com (smtp-out.google.com [216.239.44.51]) by core3.amsl.com (Postfix) with ESMTP id 1700E3A6B7B for <tcpm@ietf.org>; Mon, 15 Nov 2010 00:02:45 -0800 (PST)
Received: from wpaz24.hot.corp.google.com (wpaz24.hot.corp.google.com [172.24.198.88]) by smtp-out.google.com with ESMTP id oAF83Q00030513 for <tcpm@ietf.org>; Mon, 15 Nov 2010 00:03:26 -0800
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1289808206; bh=UUITJv5bPiwlmwWJQGMo9sxrVz0=; h=MIME-Version:In-Reply-To:References:Date:Message-ID:Subject:From: To:Cc:Content-Type:Content-Transfer-Encoding; b=xkrTI04K1KDpLks9prDBkwWSu0Wa5HJn1fg45o0eLr4+lqttpIWN1mCVGRj3bDNwP 8RfsCsBfbeLspnC0KLRKQ==
Received: from ywi6 (ywi6.prod.google.com [10.192.9.6]) by wpaz24.hot.corp.google.com with ESMTP id oAF83Oh7012948 for <tcpm@ietf.org>; Mon, 15 Nov 2010 00:03:25 -0800
Received: by ywi6 with SMTP id 6so1122478ywi.14 for <tcpm@ietf.org>; Mon, 15 Nov 2010 00:03:24 -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 :content-transfer-encoding; bh=Wgvzx+B5LLy+tyoN0N+LKpx2pntGtNdwMikPx4YtT/Q=; b=yHTeWG3WlOCg8pOBuowXoGIH9Gd1CIIjg30L6J8w4y74SCzJ7ErPAVHv54gZUIxw+A DHyICLoC7ZgRT8imD+sw==
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:content-transfer-encoding; b=pTdTvyneAcof4bouIlZd8YG91cIUPXnQ9510r/TPI8r2K8MYs8fEnjdwmpEqkIcHeR pHQalLeWLqwy4Ed1zkOA==
MIME-Version: 1.0
Received: by 10.150.91.13 with SMTP id o13mr9006212ybb.6.1289808204530; Mon, 15 Nov 2010 00:03:24 -0800 (PST)
Received: by 10.150.145.4 with HTTP; Mon, 15 Nov 2010 00:03:24 -0800 (PST)
In-Reply-To: <4CDE97D2.7010005@tlc.polito.it>
References: <20101110152857.GA5094@hell> <AANLkTi=RzbPbVRDQh7y-ydY-P7H16wDri=8EtXP5QuV3@mail.gmail.com> <20101111012453.GB2691@hell> <29E76BE6-32D9-45AD-85A1-791DAADDE520@ifi.uio.no> <AANLkTik69zRJ7XcWK7ZKCYaHPP0=Z6hnhP1SUnYP=d=8@mail.gmail.com> <824FC88F-4877-45DC-AFD9-E5272ACD7C3E@ifi.uio.no> <4CDBCA4E.8000705@tlc.polito.it> <9C745827-D861-45D0-B096-AFC3E4FE5182@ifi.uio.no> <AANLkTinMKHVf_HAQ-YT8K-Tq9jdmpqQXdgnQyS8+gAcd@mail.gmail.com> <FD7B10366AE3794AB1EC5DE97A93A37316BF44877D@EXMB01CMS.surrey.ac.uk> <4CDD493B.6000201@tlc.polito.it> <FD7B10366AE3794AB1EC5DE97A93A37316BF4314A0@EXMB01CMS.surrey.ac.uk> <4CDD59BE.60704@tlc.polito.it> <AANLkTimmPD6Q9fPJ5EKH+yQmOj9=ZkucNqAK7154KoMe@mail.gmail.com> <4CDE97D2.7010005@tlc.polito.it>
Date: Mon, 15 Nov 2010 00:03:24 -0800
Message-ID: <AANLkTimAo6s6FLdaP0C4NP8QvLqEcD1mfU1PHGg=fJb7@mail.gmail.com>
From: Jerry Chu <hkchu@google.com>
To: Marco Mellia <mellia@tlc.polito.it>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
X-System-Of-Record: true
Cc: "tcpm@ietf.org Extensions" <tcpm@ietf.org>, L.Wood@surrey.ac.uk
Subject: Re: [tcpm] 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: Mon, 15 Nov 2010 08:02:53 -0000

On Sat, Nov 13, 2010 at 5:51 AM, Marco Mellia <mellia@tlc.polito.it> wrote:
>
>
>> Browsers open lots of connections these days and we always try to cope
>> that in all our experiments.
>>
>> live:
>> To get the best possible apple-to-apple comparison when comparing IW10/IW3
>> performance on our live frontends, we split the client IPs into two (same
>> size) pools to serve IW10 and IW3 simultaneously. To our own surprise,
>> mobile hosts are among the big winners (even their browsers still open >2
>> streams per domain).  See slide 19 in our IETF 77 presentation
>
> Not surprised at all... since mobile terminal suffer higher RTT, it is quite
> straight forward to see larger benefit there.
> The point is that you cannot see the impairment of other traffic...
> It it easy to gain 20% when 20% of flows goes IW10.
>
> But what about the other 80% flows that were still using IW3? Was there any
> impairment for them?
> Easy answer: if there is no congestion and there is enough buffer space at
> the bottleneck link, then no impairment is expected.
> But if there is already some congestion, and then the bottleneck queue is
> already overloaded, then I expect  lot of impairment (and unfairness).
>
> And what would be the gain if 100% of flows goes IW10?
>
> Are the benefit larger than impairments? Then go for IW10, or even IW16.
>
> Those are questions that your data cannot answer I would say.
> Has someone run at least some simulations to see what can happen on a
> congested path?

Have you at least checked the title of our most recent presentation in
Beijing to
know it might contain some relevant data for your question?

Best,

Jerry

>
> Ciao
> Marco
> _______________________________________________
> tcpm mailing list
> tcpm@ietf.org
> https://www.ietf.org/mailman/listinfo/tcpm
>