Re: [quicwg/base-drafts] QUIC PTO is too conservative, causing a measurable regression in tail latency (#3526)

ianswett <notifications@github.com> Tue, 17 March 2020 01:36 UTC

Return-Path: <noreply@github.com>
X-Original-To: quic-issues@ietfa.amsl.com
Delivered-To: quic-issues@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9C8643A1528 for <quic-issues@ietfa.amsl.com>; Mon, 16 Mar 2020 18:36:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.436
X-Spam-Level:
X-Spam-Status: No, score=-1.436 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_IMAGE_ONLY_28=1.404, HTML_MESSAGE=0.001, HTML_OBFUSCATE_05_10=0.26, MAILING_LIST_MULTI=-1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9lwgwgJax6lL for <quic-issues@ietfa.amsl.com>; Mon, 16 Mar 2020 18:36:29 -0700 (PDT)
Received: from out-23.smtp.github.com (out-23.smtp.github.com [192.30.252.206]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 45A9D3A1526 for <quic-issues@ietf.org>; Mon, 16 Mar 2020 18:36:29 -0700 (PDT)
Received: from github-lowworker-edec459.ac4-iad.github.net (github-lowworker-edec459.ac4-iad.github.net [10.52.18.32]) by smtp.github.com (Postfix) with ESMTP id 6531B660B07 for <quic-issues@ietf.org>; Mon, 16 Mar 2020 18:36:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1584408988; bh=qg2/gnU/MUPiXqSsy/yElrW3sBGRGHtJqEw2KyQDFbw=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=YEfiH7rYeJXZcKL9guOD5ENWLBzU5jnkcAFjhSzEw+/fGCTQ85fE+pmiPRVH4f2C5 2B02ynn04BnChLdIsMqQoyBwfQjP/eMtT6zlsw7ceB4ywJqYEHpebiyV5Hp7ATJSUS w421cq96dVn9V1+tYPLNTJxObrR95YwjDQmEz22M=
Date: Mon, 16 Mar 2020 18:36:28 -0700
From: ianswett <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK54GIDDALKYD6JCFD54PQFJZEVBNHHCFNKKLA@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/3526/599833225@github.com>
In-Reply-To: <quicwg/base-drafts/issues/3526@github.com>
References: <quicwg/base-drafts/issues/3526@github.com>
Subject: Re: [quicwg/base-drafts] QUIC PTO is too conservative, causing a measurable regression in tail latency (#3526)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5e70299c56af9_60323fcfc10cd96c8134e"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: ianswett
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/ULdOA2GDyoN3gITzaSYfs5W5Q70>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <quic-issues.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic-issues/>
List-Post: <mailto:quic-issues@ietf.org>
List-Help: <mailto:quic-issues-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Mar 2020 01:36:31 -0000

Yes, I meant RFC 6298, and I just updated the original post to reflect that.

In terms of rttvar, the production data I'm seeing indicates rttvar is fairly close to 1/2 SRTT on average, which isn't so surprising given SRTT is an EWMA and for it to be on the order of SRTT, it would require estimates fairly close to 0 to balance out the higher estimates.

Unfortunately, rttvar is RTT **variation**, not RTT **variance**(or RTT stdev).  As such, I don't know if we can reason about what fraction of spurious PTOs would be within SRTT + 4*RTTVar, even if we could assume a normal distribution(which is also likely wrong, but I think the least problematic assumption at the moment).

I'd really rather not cap rttvar in any way, since I can't come up with any intellectual justification for that.  The 1.5 constant from TLP does seem a bit arbitrary, but it is larger than SRTT.

We added code in Chrome to try RTTstdev(EWMA'd), but that's even more experimental than the suggestion in my first post on this issue.  I think there's a good chance 2*RTTStdev is the best option(vs 4*RTTVar), but I don't have data to support that yet.

I reopened PR #2952 for packet number skipping.  I can open an issue if needed, but it's a simple non-normative PR.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/issues/3526#issuecomment-599833225