From: Aaron Wood <woody77@gmail.com>
To: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Still seeing bloat with a DOCSIS 3.1 modem
Date: Tue, 24 Mar 2020 22:02:27 -0700 [thread overview]
Message-ID: <CALQXh-N7GTK7Ydb57uh7bT_X2KXP2bzAzWNEmHUj4fAeiXbH9A@mail.gmail.com> (raw)
In-Reply-To: <CALQXh-PpLhvF7oYkNwMq6y9Wt2ziYLXTOyN31T39+Kw8XXZcHw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1073 bytes --]
(hit send early, somehow)...
Although this thread makes we wonder if perhaps not:
https://lists.bufferbloat.net/pipermail/cake/2018-August/004285.html
On Tue, Mar 24, 2020 at 10:01 PM Aaron Wood <woody77@gmail.com> wrote:
> 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.
>
> 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.
>
> Although
>
[-- Attachment #2: Type: text/html, Size: 2176 bytes --]
next prev parent reply other threads:[~2020-03-25 5:02 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 [this message]
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
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=CALQXh-N7GTK7Ydb57uh7bT_X2KXP2bzAzWNEmHUj4fAeiXbH9A@mail.gmail.com \
--to=woody77@gmail.com \
--cc=bloat@lists.bufferbloat.net \
/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