Re: [tcpm] TCP tuning

Andrew Yourtchenko <ayourtch@cisco.com> Thu, 04 February 2010 14:08 UTC

Return-Path: <ayourtch@cisco.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 25A973A6DAD for <tcpm@core3.amsl.com>; Thu, 4 Feb 2010 06:08:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 I8kZd3biZFEF for <tcpm@core3.amsl.com>; Thu, 4 Feb 2010 06:08:26 -0800 (PST)
Received: from av-tac-bru.cisco.com (weird-brew.cisco.com [144.254.15.118]) by core3.amsl.com (Postfix) with ESMTP id B46F13A6915 for <tcpm@ietf.org>; Thu, 4 Feb 2010 06:08:25 -0800 (PST)
X-TACSUNS: Virus Scanned
Received: from strange-brew.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-bru.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id o14E5FjC002595; Thu, 4 Feb 2010 15:05:15 +0100 (CET)
Received: from dhcp-bru-peg2-vl25-144-254-8-234.cisco.com (dhcp-bru-peg2-vl25-144-254-8-234.cisco.com [144.254.8.234]) by strange-brew.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id o14E5CRS021325; Thu, 4 Feb 2010 15:05:12 +0100 (CET)
Date: Thu, 04 Feb 2010 15:05:12 +0100
From: Andrew Yourtchenko <ayourtch@cisco.com>
X-X-Sender: ayourtch@ayourtch-lnx.stdio.be
To: "SCHARF, Michael" <Michael.Scharf@alcatel-lucent.com>
In-Reply-To: <133D9897FB9C5E4E9DF2779DC91E947C025F18D6@SLFSNX.rcs.alcatel-research.de>
Message-ID: <alpine.DEB.2.00.1002041458350.4145@ayourtch-lnx.stdio.be>
References: <7BE9742D-6EDC-43FE-84FC-D22C52D23152@nokia.com><1e41a3231002031232r6ec9edd3p6367dd9c2581fa08@mail.gmail.com> <d1c2719f1002031244g3415c8e1r7d36e26058158d20@mail.gmail.com> <133D9897FB9C5E4E9DF2779DC91E947C025F18D6@SLFSNX.rcs.alcatel-research.de>
User-Agent: Alpine 2.00 (DEB 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: MULTIPART/MIXED; BOUNDARY="8323329-568019070-1265292312=:4145"
Cc: tcpm@ietf.org
Subject: Re: [tcpm] TCP tuning
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: ayourtch@cisco.com
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 14:08:27 -0000


On Thu, 4 Feb 2010, SCHARF, Michael wrote:

> Jerry,
>
>>> - A significant increase to the initial window might benefit from
>>> introduction of some form of pacing, since you won't have any ack
>>> clock yet.  This might help reduce losses and delay jitter.
>>
>> Agreed. The question is, what is that threshold of
>> window/burst size beyond which pacing is required. My current
>> guess is > 10.
>
> I have the same impression, at least from what I have seen in simulations.
>
> Yet, one could think of a very simple form of pacing with a single 
>timer that changes the Slow-Start only when it "hurts" - I think that I 
>have mentioned this possibility on this list before:
>
> In this approach, the initial window remains at the value given by RFC 
>3390. But the sender is allowed to further increase the window after a 
>certain time (say, 100ms), but only
> if the RTT is known to be larger than 100ms (as measured e. g. during 
>handshake), if no ACK has been received until then, and if recently there 
>have been no signs of congestion to this destination.
>
> The advantage of this approach is that TCP uses the larger initial 
>window only if the RTT is larger than 100ms (or whatever threshold is 
>defined). On the one hand, this reduces the performance problems that can 
>be observed for RTTs of the order of 200ms. But, on the other hand, flows 
>with a smaller RTT would use the existing Slow-Start, i. e., the faster 
>startup is only used by a small number of flows and thus be much less 
>disruptive than a general revision of RFC 3390.
>
> A simpler variant of this idea is to allow an increased initial window 
>beyond RFC 3390 if the measured RTT is larger than a certain threshold 
>such as 100ms.

And a possible tweak to this: if we increased the initial window beyond 
RFC3390, measure the number of retransmits that have to be done for those 
segments. If the stack had to retransmit, then subsequent connection 
attempts from the host would need to reduce this "increased" window.

I think this could help to take care of the concern about the short queue 
limits on the access-layer equipment.


cheers,
andrew

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