From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from cassarossa.samfundet.no (cassarossa.samfundet.no [IPv6:2001:67c:29f4::29]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate) by huchra.bufferbloat.net (Postfix) with ESMTPS id 8B17821F2D2 for ; Wed, 22 Apr 2015 08:59:37 -0700 (PDT) Received: from pannekake.samfundet.no ([2001:67c:29f4::50] ident=unknown) by cassarossa.samfundet.no with esmtps (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from ) id 1Ykx3l-00034U-Fx; Wed, 22 Apr 2015 17:59:33 +0200 Received: from sesse by pannekake.samfundet.no with local (Exim 4.80) (envelope-from ) id 1Ykx3l-0007Kd-6G; Wed, 22 Apr 2015 17:59:33 +0200 Date: Wed, 22 Apr 2015 17:59:33 +0200 From: "Steinar H. Gunderson" To: luca.muscariello@orange.com Message-ID: <20150422155933.GA20218@sesse.net> References: <2C987A4B-7459-43C1-A49C-72F600776B00@gmail.com> <14cd9e74e48.27f7.e972a4f4d859b00521b2b659602cb2f9@superduper.net> <20150422040453.GB36239@sesse.net> <1429676935.18561.42.camel@edumazet-glaptop2.roam.corp.google.com> <12383_1429692679_55376107_12383_9099_1_p7gmr0psut68sen0sao8o4lp.1429692550899@email.android.com> <1429710657.18561.68.camel@edumazet-glaptop2.roam.corp.google.com> <25065_1429716388_5537BDA4_25065_2328_1_63pyislbvtjf653k3qt8gw2c.1429715929544@email.android.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <25065_1429716388_5537BDA4_25065_2328_1_63pyislbvtjf653k3qt8gw2c.1429715929544@email.android.com> X-Operating-System: Linux 3.18.4 on a x86_64 User-Agent: Mutt/1.5.21 (2010-09-15) Cc: bloat Subject: Re: [Bloat] RE : DSLReports Speed Test has latency measurement built-in X-BeenThere: bloat@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: General list for discussing Bufferbloat List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Apr 2015 16:00:07 -0000 On Wed, Apr 22, 2015 at 03:26:27PM +0000, luca.muscariello@orange.com wrote: > BTW if a paced flow from Google shares a bloated buffer with a non paced > flow from a non Google server, doesn't this turn out to be a performance > penalty for the paced flow? Nope. The paced flow puts less strain on the buffer (and hooray for that), which is a win no matter if the buffer is contended or not. > fq_codel gives incentives to do pacing but if it's not deployed what's the > performance gain of using pacing? fq_codel doesn't give any specific incentive to do pacing. In fact, if absolutely all devices on your path would use fq_codel and have adequate buffers, I believe pacing would be largely a no-op. /* Steinar */ -- Homepage: http://www.sesse.net/