Re: [tcpm] I-D Action: draft-ietf-tcpm-hystartplusplus-12.txt

Neal Cardwell <ncardwell@google.com> Wed, 11 January 2023 22:07 UTC

Return-Path: <ncardwell@google.com>
X-Original-To: tcpm@ietfa.amsl.com
Delivered-To: tcpm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D81FEC14CE29 for <tcpm@ietfa.amsl.com>; Wed, 11 Jan 2023 14:07:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.595
X-Spam-Level:
X-Spam-Status: No, score=-17.595 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Xxay01wSxw6F for <tcpm@ietfa.amsl.com>; Wed, 11 Jan 2023 14:07:38 -0800 (PST)
Received: from mail-vs1-xe36.google.com (mail-vs1-xe36.google.com [IPv6:2607:f8b0:4864:20::e36]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 600AFC131C62 for <tcpm@ietf.org>; Wed, 11 Jan 2023 14:07:19 -0800 (PST)
Received: by mail-vs1-xe36.google.com with SMTP id i185so17247334vsc.6 for <tcpm@ietf.org>; Wed, 11 Jan 2023 14:07:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=4jYzqBhkpo+qhPRDNaaVf+6PLNy5lLR/qJQisnjirns=; b=KB18cQI90jpSXyZRjMTqq/eC8SE6t9eLGD3+CM0N9Voe+WH/7vtOrdbig1flTLrihu LJvgFCjxM36x8rC5wXhGLsyPk/7XVjfA03o1GGx4DvJV9p3CjBu8xjNDcMcHNoX7Y8VH T6/1twEWJQrZaZRUxSB+Mu3qWa7X1sbJ4NEi4LXrDA5KXgvysMcw5zIwxGuTdOWwdlom 8rKgzgnCHtxMOK27Nb723R9AHH5F0iVUhIMtsEi0/0M4Qcv7jd+uK/V0qyMMd5ha4e+h WMiA7kIVQNEBPd9yxiUWlTmbBAxfnr4/Ux2ytMhZu1ykhEyfU2Wa0Lp1p5s7MnyITkxu ONFA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=4jYzqBhkpo+qhPRDNaaVf+6PLNy5lLR/qJQisnjirns=; b=0A//TE+ZZSS2rkrPjyKlfH6V1CVv1U8TCnuERqriGVwqabIGTAIJw4G4vH1zAc7Iza VXMib20KyTe/agvXZwMJHI5D2MKYuQuoJQuDSNtEK5FYfCU3vQQqsRTXKdPcfcLdQHVr 98w6Vt2GVPGmDBcZ19G/6Yd150gX1kc0NicQXNQQHMdSEb7g0eOSoWEMAINCbRR0y2DX HxQhniplJOPsVV+re0gUkGr7RHCoTsNX6jj0Xzko3pqfIdjN4TR14enUCgn3ZfwE3Jfa sXB0XfZycqJqnYS8jV6nZNycy+TzYOnuFaWWxvXqtyvZt4XP/JMmXGRdu6acapQCcvxc KGQg==
X-Gm-Message-State: AFqh2kqHihWlrOo4P5RR99bFRdW/qXdiWfpBWDAVvVr7GqYKLj9HZ2i3 eH6/zZceuxYWz4JeUOBx9k1GPlylqsB0NzfoJWUk+MH7mcCoag6vc2A=
X-Google-Smtp-Source: AMrXdXsiQI6bcGHEJvmPojhKKzXSKB7tWO2uq6ST0OQRsSk3JCGEBu2QSKtVwnczcARREU94cmkm+VLYDgOx471fnz0=
X-Received: by 2002:a67:cd16:0:b0:3cb:10fe:e6b6 with SMTP id u22-20020a67cd16000000b003cb10fee6b6mr7160145vsl.20.1673474837814; Wed, 11 Jan 2023 14:07:17 -0800 (PST)
MIME-Version: 1.0
References: <167330410669.3759.12442685855520700837@ietfa.amsl.com> <CADVnQymKgWE+Jx8-eTw=1nZmpgb2tAYbSUxxKVm=Rgw6W8jmVw@mail.gmail.com>
In-Reply-To: <CADVnQymKgWE+Jx8-eTw=1nZmpgb2tAYbSUxxKVm=Rgw6W8jmVw@mail.gmail.com>
From: Neal Cardwell <ncardwell@google.com>
Date: Wed, 11 Jan 2023 17:07:01 -0500
Message-ID: <CADVnQy=W+_nOk9rPPuV0yqqh1CxNz_J_d53tL40Er462CafDaw@mail.gmail.com>
To: tcpm@ietf.org
Cc: i-d-announce@ietf.org, Praveen Balasubramanian <pravb.ietf@gmail.com>, huanyi@microsoft.com, Matt Olson <maolson@microsoft.com>
Content-Type: multipart/alternative; boundary="00000000000040394a05f20439e7"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tcpm/J2vlMZdhGiiFoLpY7fzDl--Eu-k>
Subject: Re: [tcpm] I-D Action: draft-ietf-tcpm-hystartplusplus-12.txt
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcpm>, <mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 11 Jan 2023 22:07:41 -0000

Martin pointed out out-of-band that my various attempts at explaining this
point have not been clear, so let me try to express this a different way:

For about the last decade the Linux TCP default has been: [ CUBIC + Hystart
+ L=infinity + unpaced ]. This is because the commonly deployed qdiscs for
the major Linux distributions do not implement pacing.

For 2013-2016 Google/YouTube Linux TCP ran with: [ CUBIC + Hystart +
L=infinity + paced ]. This was using the fq qdisc to implement pacing.

best regards,
neal


On Tue, Jan 10, 2023 at 10:24 AM Neal Cardwell <ncardwell@google.com> wrote:

> Looks like there is still one significant word in the "Deployments and
> Performance Evaluations" section that needs to be updated to be accurate.
>
> Existing draft-ietf-tcpm-hystartplusplus-12 text:
>
>   There has been over a decade of experience using the
>   original Hystart algorithm for all TCP connections in the
>   Linux operating system with pacing *enabled* and an
>   actual L = infinity.
>
> Suggested text:
>
>   There has been over a decade of experience using the
>   original Hystart algorithm for all TCP connections in the
>   Linux operating system with pacing *disabled* and an
>   actual L = infinity.
>
> I mentioned the rationale in the "Re: [tcpm] Changes to
> draft-ietf-tcpm-hystartplusplus after WGLC" thread on Nov 29:
>
>   https://mailarchive.ietf.org/arch/msg/tcpm/CSzCgxxSLrO9u63dymyyxqB6bD4/
>
> cheers,
> neal
>
>
> On Mon, Jan 9, 2023 at 8:53 PM <internet-drafts@ietf.org> wrote:
>
>>
>> A New Internet-Draft is available from the on-line Internet-Drafts
>> directories.
>> This draft is a work item of the TCP Maintenance and Minor Extensions WG
>> of the IETF.
>>
>>         Title           : HyStart++: Modified Slow Start for TCP
>>         Authors         : Praveen Balasubramanian
>>                           Yi Huang
>>                           Matt Olson
>>   Filename        : draft-ietf-tcpm-hystartplusplus-12.txt
>>   Pages           : 9
>>   Date            : 2023-01-09
>>
>> Abstract:
>>    This document describes HyStart++, a simple modification to the slow
>>    start phase of congestion control algorithms.  Traditional slow start
>>    can overshoot the ideal send rate in many cases, causing high packet
>>    loss and poor performance.  HyStart++ uses a delay increase heuristic
>>    to find an exit point before possible overshoot.  It also adds a
>>    mitigation to prevent jitter from causing premature slow start exit.
>>
>>
>> The IETF datatracker status page for this draft is:
>> https://datatracker.ietf.org/doc/draft-ietf-tcpm-hystartplusplus/
>>
>> There is also an htmlized version available at:
>> https://datatracker.ietf.org/doc/html/draft-ietf-tcpm-hystartplusplus-12
>>
>> A diff from the previous version is available at:
>>
>> https://author-tools.ietf.org/iddiff?url2=draft-ietf-tcpm-hystartplusplus-12
>>
>>
>> Internet-Drafts are also available by rsync at rsync.ietf.org:
>> :internet-drafts
>>
>>
>> _______________________________________________
>> tcpm mailing list
>> tcpm@ietf.org
>> https://www.ietf.org/mailman/listinfo/tcpm
>>
>