General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Sebastian Moeller <moeller0@gmx.de>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: Aaron Wood <woody77@gmail.com>, bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Still seeing bloat with a DOCSIS 3.1 modem
Date: Wed, 25 Mar 2020 10:04:32 +0100	[thread overview]
Message-ID: <D12A75D5-5A19-42FA-A5DE-8CEDA95B7050@gmx.de> (raw)
In-Reply-To: <875zesret5.fsf@toke.dk>

Hi Toke,


> On Mar 25, 2020, at 09:58, Toke Høiland-Jørgensen <toke@toke.dk> wrote:
> 
> Aaron Wood <woody77@gmail.com> writes:
> 
>> I recently upgraded service from 150up, 10dn Mbps to xfinity's gigabit
>> (with 35Mbps up) tier, and picked up a DOCSIS 3.1 modem to go with it.
>> 
>> Flent test results are here:
>> https://burntchrome.blogspot.com/2020/03/bufferbloat-with-comcast-gigabit-with.html
>> 
>> tl/dr;  1000ms of upstream bufferbloat
>> 
>> But it's DOCSIS 3.1, so why isn't PIE working?  Theory:  It's in DOCSIS 3.0
>> upstream mode based on the status LEDs.  Hopefully it will go away if I can
>> convince it to run in DOCSIS 3.1 mode.
> 
> I think that while PIE is "mandatory to implement" in DOCSIS 3.1, the
> ISP still has to turn it on? So maybe yelling at them will work? (ha!)
> 
>> At the moment, however, my WRT1900AC isn't up to the task of dealing with
>> these sorts of downstream rates.
>> 
>> So I'm looking at the apu2, which from this post:
>> https://forum.openwrt.org/t/comparative-throughput-testing-including-nat-sqm-wireguard-and-openvpn/44724
>> 
>> Will certainly get most of the way there.
> 
> My Turris Omnia is doing fine on my 1Gbps connection (although that
> hardly suffers from bloat, so I'm not doing any shaping; did try it
> though, and it has no problem with running CAKE at 1Gbps).

	Well, doing local network flent RRUL stress tests indicated that my omnia (at that time with TOS4/Openwrt18) only allowed up to 500/500 Mbps shaping with bi directionally saturating traffic with full MTU-sized packets. So I undirectional CAKE at 1Gbps can work, but under full load, I did not manage that, what did I wrong?

Best Regards
	Sebastian

> 
> -Toke
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat


  reply	other threads:[~2020-03-25  9:04 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-25  5:01 Aaron Wood
2020-03-25  5:02 ` Aaron Wood
2020-03-25  5:29 ` Matt Taggart
2020-03-25  6:19   ` Sebastian Moeller
2020-03-25 15:46     ` Aaron Wood
2020-03-25  8:58 ` Toke Høiland-Jørgensen
2020-03-25  9:04   ` Sebastian Moeller [this message]
2020-03-25 11:03     ` Toke Høiland-Jørgensen
2020-03-25 15:44       ` Aaron Wood
2020-03-25 15:57       ` Aaron Wood
2020-03-25 19:18         ` Dave Taht
2020-03-28 22:46           ` Aaron Wood
2020-03-29 19:58         ` Dave Taht
2020-03-29 23:52           ` Aaron Wood
2020-03-25 18:13 ` Jim Gettys

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=D12A75D5-5A19-42FA-A5DE-8CEDA95B7050@gmx.de \
    --to=moeller0@gmx.de \
    --cc=bloat@lists.bufferbloat.net \
    --cc=toke@toke.dk \
    --cc=woody77@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox