From: Jonathan Morton <chromatix99@gmail.com>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: Sebastian Moeller <moeller0@gmx.de>,
Stuart Cheshire <cheshire@apple.com>,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] UniFi Dream Machine Pro
Date: Fri, 22 Jan 2021 23:43:13 +0200 [thread overview]
Message-ID: <05D85DE3-2438-43E9-8221-31CFC19087F8@gmail.com> (raw)
In-Reply-To: <87bldg65mg.fsf@toke.dk>
> On 22 Jan, 2021, at 11:09 pm, Toke Høiland-Jørgensen via Bloat <bloat@lists.bufferbloat.net> wrote:
>
> As Sebastian says, the source of lower performance when using SQM on
> some boxes is the traffic shaper, and sometimes the lack of hardware
> offloads.
I have a strong suspicion that on some hardware, the offload engine & switch is connected to the SoC through a link that is much slower than the Ethernet ports exposed to the outside. As long as traffic stays within the engine, it can run at line rate, but engaging rich software measures requires stuffing it all through the narrower link. This is independent of the CPU's capabilities and is purely an I/O bottleneck.
In this particular case, I believe the router portion of the Dream Machine is natively a Gigabit Ethernet device, for which good IPsec and SQM performance at 800Mbps is reasonably expected. The pair of 10G ports are part of the switch portion, and thus intended to support LAN rather than WAN traffic. Think of it as equivalent to attaching a Raspberry Pi 4 (which has native GigE) to a switch with a pair of 10G "uplink" ports for daisy-chaining to other switches.
- Jonathan Morton
next prev parent reply other threads:[~2021-01-22 21:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-20 15:55 Dave Taht
2021-01-22 19:42 ` Stuart Cheshire
2021-01-22 20:42 ` Sebastian Moeller
2021-01-22 21:09 ` Toke Høiland-Jørgensen
2021-01-22 21:43 ` Jonathan Morton [this message]
2021-01-23 23:19 ` Dave Taht
2021-01-24 6:50 ` Mikael Abrahamsson
2021-01-23 23:30 ` Dave Taht
2021-01-24 0:31 ` Nils Andreas Svee
2021-01-24 1:08 ` Nils Andreas Svee
2021-01-26 16:02 ` Dave Taht
2021-01-27 22:58 ` Nils Andreas Svee
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=05D85DE3-2438-43E9-8221-31CFC19087F8@gmail.com \
--to=chromatix99@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=cheshire@apple.com \
--cc=moeller0@gmx.de \
--cc=toke@toke.dk \
/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