IETF Logo Mail Archive

Re: [quicwg/base-drafts] DATA frame encoding is inefficient for long dynamically generated bodies (#1885)

ianswett <notifications@github.com> Fri, 19 October 2018 19:23 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 328B61310CA for <quic-issues@ietfa.amsl.com>; Fri, 19 Oct 2018 12:23:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.064
X-Spam-Level:
X-Spam-Status: No, score=-8.064 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.064, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, 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 mOENq-xYDkxq for <quic-issues@ietfa.amsl.com>; Fri, 19 Oct 2018 12:23:56 -0700 (PDT)
Received: from out-1.smtp.github.com (out-1.smtp.github.com [192.30.252.192]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 277F41310DF for <quic-issues@ietf.org>; Fri, 19 Oct 2018 12:23:43 -0700 (PDT)
Date: Fri, 19 Oct 2018 12:23:42 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1539977022; bh=IrOLkPLayFxIL1Oz6LCxXJQCCCbPIbz5UTes6CgHxUU=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=Qk1kZHNkg0WMa6R07ongHbUeNf6fsl2jiqD/SSFlsSypbcW2evnuxvRKJw8Rq576P QU0S6wjjbX3zp7+B1todogDOBSNP8BWVouo3fP1cRjQiaSttnO6OyRTpBbsISN6bYW xIolbQdAYOuMEcl5hsQYepdYA3v1qiDYXUUp89VM=
From: ianswett <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abcd2669b09933982610792a1f096ff3387dbd4ac992cf0000000117e1f13e92a169ce16286866@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/1885/431471861@github.com>
In-Reply-To: <quicwg/base-drafts/issues/1885@github.com>
References: <quicwg/base-drafts/issues/1885@github.com>
Subject: Re: [quicwg/base-drafts] DATA frame encoding is inefficient for long dynamically generated bodies (#1885)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5bca2f3eb1a73_190c3f85e80d45b41324e9"; 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/zfmu8kpc-yfYu_t6CAUZzs6bC3U>
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: Fri, 19 Oct 2018 19:23:59 -0000

@MikeBishop gQUIC currently only has this model, because it doesn't use H2 DATA frames, and the implementation is very straightforward and easy to optimize so my perspective is switched from yours.  Given there's no code shared between H2 and HTTP over QUIC, I think it's a mistake to assume we have or should inherit the region model from H2.

To reiterate what @dtikhonov and @mikkelfj are saying, for me this is more about making fast implementations that minimize copies and allocations easier to implement, and less about minimizing framing overhead.  In my case, I believe I could never send a length and all existing use cases.

-- 
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/1885#issuecomment-431471861

v2.46.0 | Report a Bug | By Email | System Status