Re: Draft: QUIC Throughput Testing
Ian Swett <ianswett@google.com> Wed, 22 September 2021 11:05 UTC
Return-Path: <ianswett@google.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 74AA53A17C5 for <quic@ietfa.amsl.com>; Wed, 22 Sep 2021 04:05:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -18.097
X-Spam-Level:
X-Spam-Status: No, score=-18.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.499, 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.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 gi2aNLEg0_SI for <quic@ietfa.amsl.com>; Wed, 22 Sep 2021 04:05:41 -0700 (PDT)
Received: from mail-qk1-x72c.google.com (mail-qk1-x72c.google.com [IPv6:2607:f8b0:4864:20::72c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B9B5D3A17C3 for <quic@ietf.org>; Wed, 22 Sep 2021 04:05:41 -0700 (PDT)
Received: by mail-qk1-x72c.google.com with SMTP id b65so7828415qkc.13 for <quic@ietf.org>; Wed, 22 Sep 2021 04:05:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=q0KFWUrLZ9FAI+yqNbJ7h7BaHZEA0eOCHoelZz4jS2I=; b=azjZbZh2cxruUcQdsmvf60nT6UvyzzcXKdMepY056sMOEBEJgNuTgrG63zSWMk67cI zqTGZz5sKBGvVK8+rbBHgKvTtIINSg5JZD2QhaDaM+FOaDkeUk/cr6OIQWhcglL4qq+2 Rzl7e1KPBjUZ7xAlB1crp7v/O2SAqN/QS3SLGnG8ixwhGGqXB5d7ag18fjtPdbUsS12f aOyg2nz7U9uCX0CjeyHDogaolocVk0N+y7BpKWV6V591oqyg4ivc76n6blkJmsGNVNLP zp/Mgjc7o3sQQf2yDKEWlyKEUKFC65g4pskAdZyjLOFxzBINAzCLA1cf1BStxwlVfaJG H4VQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=q0KFWUrLZ9FAI+yqNbJ7h7BaHZEA0eOCHoelZz4jS2I=; b=SQ2cY6maQjljqUADPiVExO/HUciIvFeHEt05S7uRQQrC3Rr//LYKjxrzR7lMjFS314 7HFyHrKdXAeU/6ztEKK8VcwOCj2skdli2ZS52S4J9BTbIpz0ZftrjLo7ZwbTZTffrC3L 1Jn5rwIYn5p48Ofc7C/utdLEiHqcV4lzPTDD1j+5MaK3rXFI7VfLeAi83EJmau+JLWE6 hN/o2awONB3I/yP5hXQv/kMcLOisFQMQqL43nYfx2c6LR3RdA7w0vXTXTlYLEkzFxru7 LAzbuO4LEq/iORBM+N8O5YRO90Ae5PkC06JgZXUrcLcpnCcR65QdXkxP7dIBfh4Lnxch GHiw==
X-Gm-Message-State: AOAM531dAZHfJQESN9LmBqvQZEx1WN+K/byni2L7uArI8nwzWDgwFLH0 RgyjtEiQO+PtXoKWMjcPIDj7DowHzN4EuUcVyqy36Q==
X-Google-Smtp-Source: ABdhPJzxE0vCpv8CbFCZMZzHho+nWRJtv2OGYWe+/O7lsPOwo6vIjAEw4rpvV3szHDg6q43IQ30YE2fzFERxFHeY0OM=
X-Received: by 2002:a25:4789:: with SMTP id u131mr44576992yba.531.1632308740065; Wed, 22 Sep 2021 04:05:40 -0700 (PDT)
MIME-Version: 1.0
References: <DM4PR11MB53417177BDF29E29E7FA57F299A29@DM4PR11MB5341.namprd11.prod.outlook.com> <20210922100925.GA16294@tom-desk.erg.abdn.ac.uk>
In-Reply-To: <20210922100925.GA16294@tom-desk.erg.abdn.ac.uk>
From: Ian Swett <ianswett@google.com>
Date: Wed, 22 Sep 2021 07:05:28 -0400
Message-ID: <CAKcm_gNyDVG7jd7pcAxvBeO0bOTAiotD6SB7SbjvD66ZT2Q5zA@mail.gmail.com>
Subject: Re: Draft: QUIC Throughput Testing
To: Tom Jones <tom@erg.abdn.ac.uk>
Cc: Kévin Corre <kevin.corre@exfo.com>, "quic@ietf.org" <quic@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000009e4ca805cc937ee0"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/HzzbZvje29fX98nezZqI3TGMW98>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Sep 2021 11:05:47 -0000
I would suggest looking at the ACK frequency draf <https://datatracker.ietf.org/doc/draft-ietf-quic-ack-frequency/>t, or some similar approaches. Otherwise it can be very difficult to achieve comparable speeds as TCP. See Fastly's nice post <https://www.fastly.com/blog/measuring-quic-vs-tcp-computational-efficiency> about what it took to get comparable performance in QUIC as TCP. On Wed, Sep 22, 2021 at 6:06 AM Tom Jones <tom@erg.abdn.ac.uk> wrote: > On Wed, Sep 22, 2021 at 09:15:58AM +0000, Kévin Corre wrote: > > Hi everyone, > > > > Our team at EXFO is working on adapting the TCP Throughput Testing > methodology described in RFC6349 to QUIC. We just published a draft that > can be found at > https://datatracker.ietf.org/doc/html/draft-corre-quic-throughput-testing > > The draft follows the same organization as the RFC6349 and discuss what > should be changed to support QUIC Throughput Testing. > > The methodology is interested in measuring the achievable QUIC > throughput and efficiency of a managed network when the connection is at an > equilibrium. Although, it could also be used for un-managed networks. > > > > We are particularly looking for comments on the way we use the protocol > to measure the network's QUIC Throughput but also feedback from potential > users of such a test. > > For instance, our draft closely follows the RFC6349 methodology, but > since QUIC introduces new features, it would be interesting to gauge > interest in extending the methodology to test features such as 0-RTT effect. > > > > Comments would be gladly appreciated, so let us know what you think. > > > > Hi Kévin, > > Have you seen draft-banks-quic-performance? I don't see a reference to > it in your document. This protocol has implementations using a number of > quic different libraries. > > There is also a perf channel on the quic slack, please ask off list if > you require an invite. > > https://datatracker.ietf.org/doc/html/draft-banks-quic-performance-00.txt > > - Tom > >
- Draft: QUIC Throughput Testing Kévin Corre
- Re: Draft: QUIC Throughput Testing Tom Jones
- Re: Draft: QUIC Throughput Testing Ian Swett
- Re: [E!] : Re: Draft: QUIC Throughput Testing Kévin Corre
- Re: [E!] : Re: Draft: QUIC Throughput Testing Ian Swett