Re: [quicwg/base-drafts] Add a section on flow control performance (#3793)

krasic <notifications@github.com> Tue, 07 July 2020 23:24 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 CAAA03A0C02 for <quic-issues@ietfa.amsl.com>; Tue, 7 Jul 2020 16:24:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.1
X-Spam-Level:
X-Spam-Status: No, score=-3.1 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_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 JEQvDXN4MqOL for <quic-issues@ietfa.amsl.com>; Tue, 7 Jul 2020 16:24:36 -0700 (PDT)
Received: from out-22.smtp.github.com (out-22.smtp.github.com [192.30.252.205]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4C2E73A0B6B for <quic-issues@ietf.org>; Tue, 7 Jul 2020 16:24:36 -0700 (PDT)
Received: from github-lowworker-f62aa54.va3-iad.github.net (github-lowworker-f62aa54.va3-iad.github.net [10.48.17.68]) by smtp.github.com (Postfix) with ESMTP id 88F93A1F4A for <quic-issues@ietf.org>; Tue, 7 Jul 2020 16:24:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1594164275; bh=m9Pp33HjslZIWAErg0aWfc+FEyLMQ91kT6nDuLxhK6Y=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=1c+l03hi1FsYv1vHr9MiQxO1j3LW8OMHirLzYzB7dHJ7ic7gUEwW31ir1hgKiL56c mHPzgBNp0Qwrtu0IuDc7aaJIiHwjOtAbEvCoz6XZgIcJlQ76LSy+MEimoa+4y3aU9l kJdNgiayrK2D0wYmE8X0nv9enpibLM3dLP0ap3UA=
Date: Tue, 07 Jul 2020 16:24:35 -0700
From: krasic <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJKY4F43AN2SMJE4AQFN5CDSTHEVBNHHCNAR3C4@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/3793/c655190036@github.com>
In-Reply-To: <quicwg/base-drafts/pull/3793@github.com>
References: <quicwg/base-drafts/pull/3793@github.com>
Subject: Re: [quicwg/base-drafts] Add a section on flow control performance (#3793)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5f05043378eca_5b613fb362ecd95c463f4"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: krasic
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/cEFkqj4hT6j8VP1GkfOy17LEd0g>
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, 07 Jul 2020 23:24:38 -0000

On Fri, Jun 26, 2020, 12:31 AM Martin Thomson <notifications@github.com>
wrote:

> QUIC doesn't really address the question of tuning flow control very
> well. This just admits that fact.
>
> It also indicates why: which essentially boils down to "RAM is cheap".
>
Hi Martin. I stumbled across this.  I don't know if you are joking, but if
not I'd like to disagree.  There are a significant class of devices,
commodity streaming devices, which are very large volume but for which the
trend is to shave as much RAM budget as possible, HD video devices in
markets like India, Brazil, etc.  In aggregate, these devices consume a
significant amount of overall internet traffic.    RAM is cheap is most
definitely not true there, and they certainly don't ship with TCP receive
windows anywhere near as large as other device segments.  This is not a
legacy issue either, for the foreseeable future it looks like the amount of
RAM in newer devices will be lucky to stay stable as opposed to even
decrease.

> Closes #3722 <https://github.com/quicwg/base-drafts/issues/3722>.
> ------------------------------
> You can view, comment on, or merge this pull request online at:
>
>   https://github.com/quicwg/base-drafts/pull/3793
> Commit Summary
>
>    - Add a section on flow control performance
>
> File Changes
>
>    - *M* draft-ietf-quic-transport.md
>    <https://github.com/quicwg/base-drafts/pull/3793/files#diff-db016291106766877c4921a79f8596e0>
>    (18)
>
> Patch Links:
>
>    - https://github.com/quicwg/base-drafts/pull/3793.patch
>    - https://github.com/quicwg/base-drafts/pull/3793.diff
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/quicwg/base-drafts/pull/3793>, or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/ABRABBQI2QR6RBOI65V4JCLRYRFDHANCNFSM4OJCIA6A>
> .
>


-- 
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/pull/3793#issuecomment-655190036