Re: [tcpm] TCP tuning

"SCHARF, Michael" <Michael.Scharf@alcatel-lucent.com> Thu, 04 February 2010 13:58 UTC

Return-Path: <Michael.Scharf@alcatel-lucent.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 4D59F3A683A for <tcpm@core3.amsl.com>; Thu, 4 Feb 2010 05:58:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.249
X-Spam-Level:
X-Spam-Status: No, score=-6.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4]
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 KBTS1PhNVc-y for <tcpm@core3.amsl.com>; Thu, 4 Feb 2010 05:58:34 -0800 (PST)
Received: from mailrelay2.alcatel.de (mailrelay2.alcatel.de [194.113.59.96]) by core3.amsl.com (Postfix) with ESMTP id 49A2C3A680E for <tcpm@ietf.org>; Thu, 4 Feb 2010 05:58:34 -0800 (PST)
Received: from SLFSNX.rcs.alcatel-research.de (slfsn1.rcs.de.alcatel-lucent.com [149.204.60.98]) by mailrelay2.alcatel.de (8.13.8/8.13.8/ICT) with ESMTP id o14DxEsq022297; Thu, 4 Feb 2010 14:59:14 +0100
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.5
Date: Thu, 04 Feb 2010 14:59:13 +0100
Message-ID: <133D9897FB9C5E4E9DF2779DC91E947C025F18DB@SLFSNX.rcs.alcatel-research.de>
In-Reply-To: <d1c2719f1002031110v3b76ca9eu14c9a110847548e7@mail.gmail.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [tcpm] TCP tuning
Thread-Index: AcqlBUv5EM/mMAFNQkW1dlL1MkDgcwAmobZQ
References: <7BE9742D-6EDC-43FE-84FC-D22C52D23152@nokia.com> <133D9897FB9C5E4E9DF2779DC91E947C025F1861@SLFSNX.rcs.alcatel-research.de> <d1c2719f1002031110v3b76ca9eu14c9a110847548e7@mail.gmail.com>
From: "SCHARF, Michael" <Michael.Scharf@alcatel-lucent.com>
To: tcpm@ietf.org, Jerry Chu <hkchu@google.com>
X-Scanned-By: MIMEDefang 2.57 on 149.204.45.73
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: Thu, 04 Feb 2010 13:58:35 -0000

Jerry,

> Actually our data points to the contrary - the average web 
> object and page size have been rising steadily. E.g., the 
> majority of our search responses no longer fit in 3 MSS these days.

OK. I looked at some traffic traces from the year 2008, which might not
be representative any more.

> > In the past, I have played a little bit with an initial 
> window e. g. 
> > of 10 MSS, and that worked surprisingly well.
> 
> Good to know!
> 
> >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.
> 
> We are planning to submit an I-D on raising initcwnd to 10MSS before
> 3/1 to be included in the upcoming IETF meeting.

Please note that I used the value of 10 MSS just as an example. I'd
actually expect that doubling the allowed initial window would be
sufficient in order to solve most real-world Slow-Start performance
issues.

Michael