From: Sebastian Moeller <moeller0@gmx.de>
To: Kenneth Porter <shiva@sewingwitch.com>
Cc: bloat <bloat@lists.bufferbloat.net>,
cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Bloat] tp-link request for SQM
Date: Fri, 3 Dec 2021 11:40:30 +0100 [thread overview]
Message-ID: <C3EBDFE9-4EB9-4F2A-8EDB-A4ED1BB46B5D@gmx.de> (raw)
In-Reply-To: <83C9FEF4F6F75A417279EDF8@[192.168.1.16]>
> On Dec 3, 2021, at 11:10, Kenneth Porter <shiva@sewingwitch.com> wrote:
>
> --On Thursday, December 02, 2021 10:48 AM -0800 Dave Taht <dave.taht@gmail.com> wrote:
>
>> tp-link, is, so far as I know, the last major home router vendor NOT
>> shipping a SQM system. Perhaps this could be modded up with someones
>> with accounts?
>>
>> https://community.tp-link.com/us/home/forum/topic/511156
>
> I just signed up an account and will add my vote.
>
> I just bought an Archer 20 to replace my old 2016 Zyxel running OpenWrt. I'd found it by looking at various reviews of "best OpenWrt router for 2021". I just updated my Zyxel firmware from v18 to v20 firmware. I get about 280 Mbps from Xfinity. I turned on cake and it dropped by 50%! So I think the old router's CPU isn't up to it. I'll be swapping in the TP-Link soon so I can turn on cake without the big performance hit.
Getting low latency traffic shaping to work in a robust and reliable way above say ~100Mbps is still a challenge even for relatively recent router SoCs. Modern multicore SoCs upped the ante in the things-to-look-out for area by adding CPU power-saving (especially frequency scaling) and load distribution over CPUs to the mix... Now even something like a raspberry pi 4B with an additional well-selected USB3 gigabit ethernet dongle (costing less than 100 EUR all in all) will allow cake up to 1/1 Gbps but still requires careful configuration to do so. No idea whether an archer 20 will do (not even sure what model that is, here in Germany I see either an C20 or an AX20 but no plain unadorned 20). If you should try OpenWrt on that thing, the OpenWrt forum is a good place to ask for configuration advice for specific models (will obviously not help if you stick to the manufacturer's firmware).
Regards
Sebastian
>
>
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
next prev parent reply other threads:[~2021-12-03 10:40 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-02 18:48 Dave Taht
2021-12-03 10:10 ` Kenneth Porter
2021-12-03 10:40 ` Sebastian Moeller [this message]
2021-12-03 12:12 ` Wheelock, Ian
2021-12-03 12:43 ` Kenneth Porter
[not found] ` <A5CB878868B38B2F0660B051@192.168.1.16>
2021-12-03 14:23 ` Dave Taht
2021-12-03 12:38 ` Kenneth Porter
2021-12-03 11:59 ` Luca Muscariello
2021-12-03 14:18 ` Dave Taht
2021-12-03 14:35 ` [Bloat] [Cerowrt-devel] " Sebastian Moeller
2021-12-03 14:58 ` Luca Muscariello
2021-12-09 16:09 ` Sebastian Moeller
2021-12-09 17:38 ` Luca Muscariello
2021-12-09 18:23 ` Sebastian Moeller
2021-12-09 18:54 ` Luca Muscariello
[not found] <mailman.1000.1638532808.1267.bloat@lists.bufferbloat.net>
2021-12-03 13:40 ` [Bloat] " Rich Brown
2021-12-03 14:30 ` Wheelock, Ian
2021-12-03 14:36 ` Dave Taht
2021-12-03 14:35 ` Dave Taht
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=C3EBDFE9-4EB9-4F2A-8EDB-A4ED1BB46B5D@gmx.de \
--to=moeller0@gmx.de \
--cc=bloat@lists.bufferbloat.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=shiva@sewingwitch.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