From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-it0-x22f.google.com (mail-it0-x22f.google.com [IPv6:2607:f8b0:4001:c0b::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 48F5C3B29E for ; Tue, 24 Jul 2018 14:08:40 -0400 (EDT) Received: by mail-it0-x22f.google.com with SMTP id d16-v6so6550429itj.0 for ; Tue, 24 Jul 2018 11:08:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mithrandi.net; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=T1qs+AVCHzsJEO88dsisU31bjMAG6tF51zPYXJqeIiE=; b=Q3qzdobPxvVAleBLNgSmb/IKZ4O4cdDALBHd2Kr4TIr+NGQxuNqxeTc1jhEJ7LIQVd rn81TnMOEWfYvuU+3YxDGfpyXbUzKQJEL5gHu5bk6iNcQTdH3wpRTUGi3TaqmzJweS/h v1IX3kT1Mn5Wgg3EJS5wJLCEPj8LdHXBeKQWo= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=T1qs+AVCHzsJEO88dsisU31bjMAG6tF51zPYXJqeIiE=; b=OoRqDamYVVUik3hZB9E9/N8Jjg6Vssqsth30P1D0CguMCjvqj5yCKcKNpe0aQmWFlB WvEpoyc+hk8yHL7xW2j9wETvx7yENOAn6d8OgIkHoUH+8/b8GG06lHN0dirtllQSceJw HnAC0Lx20ldRNfsYRmcXcS0aeKK4GUMcb3kGrbaZRifdBZN1CIXgUjJSG4Sb0AOly4rw 8fZp5DjH2BqG2oluFNNrpOhyWavekSegfl5P8GXjbKenLOyV/ivbizb7wag3uhB7K9jD Z0Iz57yavDoUjfl6AyGtMnlMQKF9rbMNyG/JAxMWzRZwADNw+7QH6BaFMvP1yPqAYXA1 ERiw== X-Gm-Message-State: AOUpUlE/3NnLubLZ//vMzBSvu4KYMNYJwAyYT0QJvtTqWKTEt9iHrV3h TKMGyrXxapZH25gLAUH9tCgMi3b29/2Yo3TaO8viBtpF8Us= X-Google-Smtp-Source: AAOMgpeBabw2zrX6ypGrG9UU8cYipZgLUVeC5E1bgcGUR5Tdb0ZqjcGCu16CiekZCoBjbmLG6VoH3rSkVyFwvn/86/M= X-Received: by 2002:a24:4254:: with SMTP id i81-v6mr3412840itb.95.1532455719771; Tue, 24 Jul 2018 11:08:39 -0700 (PDT) MIME-Version: 1.0 References: <4C129A60-21D3-4B78-A764-DC8E2CD7E4DF@gmail.com> <6839ba220fe4399eba3620620515fc1dd801a509.camel@gmail.com> <31193A5B-88BF-4EA6-9BF6-530564B93228@darbyshire-bryant.me.uk> <09E00B24-63DA-42B3-AC60-155AC76C0CC4@darbyshire-bryant.me.uk> In-Reply-To: From: Tristan Seligmann Date: Tue, 24 Jul 2018 20:08:27 +0200 Message-ID: To: Dave Taht Cc: Kevin Darbyshire-Bryant , Cake List Content-Type: multipart/alternative; boundary="000000000000cfbcd20571c2a672" Subject: Re: [Cake] inbound cake or fq_codel shaping fails on cable on netflix reno X-BeenThere: cake@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: Cake - FQ_codel the next generation List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Jul 2018 18:08:40 -0000 --000000000000cfbcd20571c2a672 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable I should note that I think the ER-X is running out of CPU at times in this configuration, so that may contribute to the weirdness somewhat. On Tue, 24 Jul 2018 at 20:05 Tristan Seligmann wrote: > Here's my results from South Africa. Ping test while running the fast.com > test, and the tcp_ndown test, running Cake on an EdgeRouter X. I get 140 = / > 140 Mbps on the fast.com test with 1ms unloaded and 6ms loaded. > > Not sure why throughput is so low, but I often see something like this on > artificial bandwidth tests; it peaks close to 200, but then drops back do= wn > toward the end of the test. I'm shaping to 200 / 200 Mbps with cake which > is my sold connection speed; the actual link is 1 Gbps active ethernet ov= er > fibre with the ISP limiting to about 210-220 Mbps. > > > On Tue, 24 Jul 2018 at 17:19 Dave Taht wrote: > >> cdfs help. I also try to encourage sending the flent.gz files too. :) >> >> Outbound, to 99% or more of the rate, *with perfect framing* looks great >> so far, 'cept on crappy cablemodems. >> >> I am concerned about recommending values as high as 98% for inbound >> shaping. We are engineering to >> the test here (2? 3 flows? on a very short rtt), and need to leave *some= * >> headroom for multiple flows to enter in slow start and get kicked out of= it. >> >> I'll buy that the old 85% figure made sense in the sub 20Mbit era, and >> that we only need enough headroom to allow X flows to enter based on the >> characteristics of the link and typical traffic - 15 new flows per secon= d >> * per active user/10 ? and cake's response to slow start is more >> agressive... >> >> try a: >> >> flent -H flent-london.bufferbloat.net -s .02 --te=3Ddownload_streams=3D3= 2 -t >> '98%' tcp_ndown >> >> with htb+fq_codel and cake to see that spike more clearly. >> >> >> On Tue, Jul 24, 2018 at 7:54 AM Kevin Darbyshire-Bryant < >> kevin@darbyshire-bryant.me.uk> wrote: >> >>> >>> >>> On 24 Jul 2018, at 14:51, Dave Taht wrote: >>> >>> Now that you can join the party, I note there IS a flent server in >>> england with irtt on it. >>> >>> flent-london.bufferbloat.net >>> >>> >>> Ok, well if you=E2=80=99re desperately interested=E2=80=A6.. :-) >>> >>> Plot I did running to the london server, one shaped at 99% downstream, >>> the other at 98%=E2=80=A6. and I=E2=80=99ve decided to stick at 98% as = a result - plot is a >>> little bit hard to distinguish but I=E2=80=99d say there=E2=80=99s arou= nd 8ms avg less >>> latency-ish between the two. And an order of magnitude between using >>> london v fremont :-) >>> >>> The upstream barely registers >>> >>> # tc -s qdisc show dev ifb4eth0 >>> qdisc cake 801a: root refcnt 2 bandwidth 78400Kbit diffserv3 >>> dual-dsthost nat ingress split-gso rtt 100.0ms ptm overhead 26 >>> >>> >>> >> >> -- >> >> Dave T=C3=A4ht >> CEO, TekLibre, LLC >> http://www.teklibre.com >> Tel: 1-669-226-2619 >> _______________________________________________ >> Cake mailing list >> Cake@lists.bufferbloat.net >> https://lists.bufferbloat.net/listinfo/cake >> > --000000000000cfbcd20571c2a672 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I should note that I think the ER-X is running out of CPU = at times in this configuration, so that may contribute to the weirdness som= ewhat.

On Tue, 24 Jul = 2018 at 20:05 Tristan Seligmann <mithrandi@mithrandi.net> wrote:
<= br>
cdfs help. I also try to encourage sending the flent.gz f= iles too. :)

Outbound, to 99% or more of the rate, *with= perfect framing* looks great so far, 'cept on crappy cablemodems.

I am concerned about recommending values as high as 98= % for inbound shaping. We are engineering to
the test here (2? 3 = flows? on a very short rtt), and need to leave *some* headroom for multiple= flows to enter in slow start and get kicked out of it.

I'll buy that the old 85% figure made sense in the sub 20Mbit era= , and that we only need enough headroom to allow X flows to enter based on = the
characteristics of the link and typical traffic - 15 new flow= s per second * per active user/10 ? and cake's response to slow start i= s more agressive...

try a:=C2=A0

flent -H flent-london.bufferbloat.net -s .02 --te=3Ddownload_streams=3D3= 2 -t '98%' tcp_ndown

with htb+fq_codel and= cake to see that spike more clearly.=C2=A0


<= div class=3D"gmail_quote">
On Tue, Jul 24, 2018 at 7:54 AM = Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk> wrote:
<= blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px= #ccc solid;padding-left:1ex">


On 24 Jul 2018, at 14= :51, Dave Taht <dave.taht@gmail.com> wrote:

Now that you can join the party,= I note there IS a flent server in england with irtt on it.

flent-london.bufferbloa= t.net

Ok, well if you=E2=80=99re desperately i= nterested=E2=80=A6.. :-)

Plot I did running to the= london server, one shaped at 99% downstream, the other at 98%=E2=80=A6. an= d I=E2=80=99ve decided to stick at 98% as a result - plot is a little bit h= ard to distinguish but I=E2=80=99d say there=E2=80=99s around 8ms avg less = latency-ish between the two.=C2=A0 And an order of magnitude between using = london v fremont :-)

The upstream barely registers=

# tc -s qdisc show dev ifb4eth0
qdisc cake 8= 01a: root refcnt 2 bandwidth 78400Kbit diffserv3 dual-dsthost nat ingress s= plit-gso rtt 100.0ms ptm overhead 26=C2=A0




--

Dave T=C3=A4ht
CEO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-669-226-2= 619
_______________________________________________
Cake mailing list
Cake@lists.= bufferbloat.net
https://lists.bufferbloat.net/listinfo/cake
--000000000000cfbcd20571c2a672--