Re: [tcpm] TCP tuning

Jerry Chu <hkchu@google.com> Wed, 03 February 2010 19:18 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 507A73A6CD1 for <tcpm@core3.amsl.com>; Wed, 3 Feb 2010 11:18:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.977
X-Spam-Level:
X-Spam-Status: No, score=-102.977 tagged_above=-999 required=5 tests=[AWL=-1.000, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 W8qsyIjQVhH9 for <tcpm@core3.amsl.com>; Wed, 3 Feb 2010 11:18:03 -0800 (PST)
Received: from smtp-out.google.com (smtp-out.google.com [216.239.44.51]) by core3.amsl.com (Postfix) with ESMTP id 50EF83A6CCB for <tcpm@ietf.org>; Wed, 3 Feb 2010 11:18:03 -0800 (PST)
Received: from wpaz21.hot.corp.google.com (wpaz21.hot.corp.google.com [172.24.198.85]) by smtp-out.google.com with ESMTP id o13JIjBd018395 for <tcpm@ietf.org>; Wed, 3 Feb 2010 11:18:45 -0800
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1265224725; bh=Bz/k5buhhysSexhJxVOGRTWHE8I=; h=MIME-Version:In-Reply-To:References:Date:Message-ID:Subject:From: To:Cc:Content-Type:Content-Transfer-Encoding; b=a56buTmV5CemCnLvQei6AxUs6jw8CDXDLUXfNRYW6RP/ke7EDxZeYN9Pak8Mcu4PU kEfDPK+9gP975EpAxulHQ==
DomainKey-Signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns; h=mime-version:in-reply-to:references:date:message-id:subject:from:to: cc:content-type:content-transfer-encoding:x-system-of-record; b=ZM/rNYtu/KPMjf+RoIf2rcPu/ArHooj8SvjX3YNtBHqsRhWFdZdAxqZQ+VqxOQoWI 756dwIztsdQ23WDiOr+6Q==
Received: from pzk6 (pzk6.prod.google.com [10.243.19.134]) by wpaz21.hot.corp.google.com with ESMTP id o13JIbtY001677 for <tcpm@ietf.org>; Wed, 3 Feb 2010 11:18:44 -0800
Received: by pzk6 with SMTP id 6so479705pzk.18 for <tcpm@ietf.org>; Wed, 03 Feb 2010 11:18:40 -0800 (PST)
MIME-Version: 1.0
Received: by 10.141.89.2 with SMTP id r2mr5412747rvl.277.1265224720110; Wed, 03 Feb 2010 11:18:40 -0800 (PST)
In-Reply-To: <4B69A0BD.2060708@sun.com>
References: <7BE9742D-6EDC-43FE-84FC-D22C52D23152@nokia.com> <133D9897FB9C5E4E9DF2779DC91E947C025F1861@SLFSNX.rcs.alcatel-research.de> <4B69A0BD.2060708@sun.com>
Date: Wed, 03 Feb 2010 11:18:40 -0800
Message-ID: <d1c2719f1002031118u2c7cb14fq74f90961c67fa4c1@mail.gmail.com>
From: Jerry Chu <hkchu@google.com>
To: Kacheong Poon <kacheong.poon@sun.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
X-System-Of-Record: true
Cc: tcpm@ietf.org
Subject: Re: [tcpm] TCP tuning
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, 03 Feb 2010 19:18:04 -0000

On Wed, Feb 3, 2010 at 8:13 AM, Kacheong Poon <kacheong.poon@sun.com> wrote:
> On 02/ 3/10 11:17 PM, SCHARF, Michael wrote:
>
>> In the past, I have played a little bit with an initial window e. g. of
>> 10 MSS, and that worked surprisingly well. Also, one could combine a
>> larger initial window with other mechanisms that would reduce the
>> aggressiveness of the flow startup. Maybe it is indeed time to think
>> about the Slow-Start once again.
>
>
> FWIW, I've come across traces showing some network equipment
> uses an initial window as large as 16 segments (some kind of
> turbo mode).  It is probably true many stacks already use a
> much larger initial window than recommended in the RFC.  Just
> that people have been very quiet about this.

Indeed, the percentage of non-compliance can be quite high, as high
as ~15% in one dataset reported by an IMC paper "TCP Revisited: A
Fresh Look at TCP in the Wild"

Jerry

>
>
>
> --
>
>                                                K. Poon.
>                                                kacheong.poon@sun.com
>
> _______________________________________________
> tcpm mailing list
> tcpm@ietf.org
> https://www.ietf.org/mailman/listinfo/tcpm
>