From: Sebastian Moeller <moeller0@gmx.de>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: "Livingood, Jason" <Jason_Livingood@comcast.com>,
"bloat@lists.bufferbloat.net" <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Really getting 1G out of ISP?
Date: Tue, 29 Jun 2021 22:09:59 +0200 [thread overview]
Message-ID: <2B2C492B-041E-46B2-A4CA-F2B47E77EEFB@gmx.de> (raw)
In-Reply-To: <20210629124831.6de2c1b9@hermes.local>
Hi Stephen,
> On Jun 29, 2021, at 21:48, Stephen Hemminger <stephen@networkplumber.org> wrote:
>
> On Tue, 22 Jun 2021 22:51:18 +0000
> "Livingood, Jason" <Jason_Livingood@comcast.com> wrote:
>
>>> It doesn't help that all the local ISP's claim 10Mbit upload even with 1G download. Is this a head end provisioning problem or related to Docsis 3.0 (or later) modems?
>>
>> I'll cover this in an upcoming technical paper (mid-July I hope). Depending on the DOCSIS version, CMTS, and cable modems involved you may have no AQM, or buffer controls for the cable modem, or AQM (sort of) on the CMTS and in the cable modem. In the Comcast network you should find AQM in the upstream queue on the cable modems for which we have deployed RDK-B software (XB6 and XB7), while other devices would have buffer controls.
>>
>> JL
>>
>
> Just a short update. The cable modem matters. Updated from Docsis 3.0 modem with bad Intel Puma chipset
> to new model with Docsis 3.1 and Broadcom and things are much more stable.
Glad that helped, rather sad state of affairs that these devices are still in the field. (I am not fan of forced obsolescence or retiring hardware too early, but these devices are simply barely fit for their purpose).
>
> As far as AQM, in this setup; fq_codel does much better than the Cake configuration. With fq_codel can
> see 700Mbit download speed. It looks like Cake is using more CPU
Yepp, it turns out that all the additional features cake brings to the table have some computational cost. At some earlier state in development cake was leaner and meaner than HTB+fq_codel, but that did not seem to hold.
> especialy since the Cake configuration
> is using an ifb ingress queue discipline as well.
Both cake and HTB+fq_codel require tricks for download shaping, either a veth pair or an IFB (both seem to have a similar cost but IFB is much simpler to set up) or for a wired only shaper, one can instantiate the internet-download shaper as egress shaper on the interface towards the LAN. Last I tested on an ancient single core 750 MHz MIPS, avoiding the IFB got a 5% higher shaper limit, so not nothing, but also not a way to have your router punch one weight class higher?
Best Regards
Sebastian
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
prev parent reply other threads:[~2021-06-29 20:10 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-22 4:00 Stephen Hemminger
2021-06-22 6:12 ` Sebastian Moeller
2021-06-22 7:44 ` Giuseppe De Luca
2021-07-06 22:31 ` Aaron Wood
2021-07-07 2:26 ` Dave Taht
2021-07-07 2:53 ` Aaron Wood
2021-07-08 19:56 ` [Bloat] [Cake] " David P. Reed
2021-06-22 23:04 ` [Bloat] " Livingood, Jason
2021-06-23 15:56 ` Stephen Hemminger
2021-07-06 22:13 ` Aaron Wood
2021-07-06 22:28 ` Wheelock, Ian
2021-07-06 22:40 ` Aaron Wood
2021-07-07 2:10 ` Dave Taht
2021-07-07 9:27 ` Wheelock, Ian
2021-07-07 16:17 ` Jonathan Morton
2021-07-07 16:24 ` Wheelock, Ian
2021-06-22 22:51 ` Livingood, Jason
2021-06-29 19:48 ` Stephen Hemminger
2021-06-29 20:09 ` Sebastian Moeller [this message]
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=2B2C492B-041E-46B2-A4CA-F2B47E77EEFB@gmx.de \
--to=moeller0@gmx.de \
--cc=Jason_Livingood@comcast.com \
--cc=bloat@lists.bufferbloat.net \
--cc=stephen@networkplumber.org \
/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