Re: [quicwg/base-drafts] Pacing when under-utilizing the Congestion Window (#2686)

MikkelFJ <> Sat, 11 May 2019 06:02 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id ECF8B12022E for <>; Fri, 10 May 2019 23:02:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.918
X-Spam-Status: No, score=-6.918 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_16=1.092, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id ZPdzXEyf4DdZ for <>; Fri, 10 May 2019 23:02:55 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 43783120112 for <>; Fri, 10 May 2019 23:02:55 -0700 (PDT)
Date: Fri, 10 May 2019 23:02:53 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1557554574; bh=P/JwUAH8YdUgL9XZRVKBKpilf+7TijtlDNBi+4RVyN0=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=Q2qdcsiRsIBYUPLOdY8qkxlRy2NtKaBX0t93/HsOGVlTwtIvIiU+hHFGe1jnb7Uhj sZzQ0rCO0MEc1Jrrb84H3vRL3blPry/n4BJwxy+1XItKGO3AuI65gvOOt0uqp/7BNX MgoY7CATiWDnjwgulKQCvhLl45A4TxZSoa92fHnw=
From: MikkelFJ <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/2686/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] Pacing when under-utilizing the Congestion Window (#2686)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5cd6658de93ef_289a3fe66bccd96811383a"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: mikkelfj
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
Archived-At: <>
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Sat, 11 May 2019 06:02:57 -0000

>  general max burst size

Is there such a thing. I'm wondering: if you use pacing, you still want to cluster your transmissions so you don't get too frequent timer interrupts unless the network adapter is capable of pacing. So how do you decide the granularity of bursts when pacing?

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub: