While it's completely right, even when having read it fully, it isn't so easy to understand unless the reader knows some things (see https://news.ycombinator.com/item?id=50588459 and its children), namely:
* That the "packet size 1024 bMaxBurst 3" (making the 4 KiB window size) is fixed for the whole connection, determined by the RTL8156B, and cannot be negotiated higher, no matter if the monitor is in between or not.
* That this window size is large enough for the NIC---Mac connection to run at full speed, but not enough for the NIC---Monitor-USB-Hub---Mac connection to run at full speed, because the added latency makes the BDP too large.
* If possible to measure, it might be illustrative to measure the NIC---Mac latency without hub directly, to compare it with the `7.6 µs` number going through the monitor (like cibyr suggested). That'd make it more obvious that the monitor increases the latency.
And I agree with dcrazy's sibling comment that the RTL8156B in the UGREEN _is_ to blame. It uses a send window size that cannot possibly deliver the advertised bandwidth behind a hub.
Anyway, great post that shows that just because you buy a device that says N Gbit/s and delivers N Gbit/s when directly attached, you cannot be sure that it'll be equally fast when attached to a form of "longer cable".
That said, I think you’re being too charitable to UGREEN. They shouldn’t advertise a product as 2.5Gb/s if it can’t actually transfer 2.5Gb/s to the host when the signal path includes a hub.
Typical Apple shit. Never had an issue with my Lenovo dock and 2.5G. Additionally, not having an eth adapter built in, in 2026, is enshittified hardware. Typical Apple again