Meta:
> Somehow I am one of those few very lucky people to have the opportunity of owning a 2.5 gig symmetrical line for my internet.
I'm not going to complain against more bandwidth (as a GenXer I stared my online journey at (IIRC) 9600bps (maybe lower)), but I'm curious to know how many residential use-cases can take advantage of that much bandwidth. Linux ISOs?
How many services allow that much speed on a single stream / (TCP) session? Maybe you could have five at 500 Mbps?
Certainly downloading security updates or games may be quicker, but I would think that above 500Mbps (and certainly 1 Gbps) there would be major diminishing returns. Is anyone regularly getting close to that utilization in their daily work / hobbies?
Better description: "My USB network switch was cutting my download speed".
The fact that it's a monitor is a little bit irrelevant.
I have nothing useful to add other than I feel so validated reading this. Ive been struggling with this issue on and off for over a year. With the release of Astra, it was able to finally unstick me to the point of enabling flow control which has been good enough.
I experienced this problem with a macbook and a thunderbolt dock. I had tried multiple different brands of docks and ethernet adapters, and various macbooks. One interesting thing I discovered is if I plugged a non-thunderbolt cable between the dock and the laptop, I would achieve full speed with no packet loss, so interestingly the issue doesn't occur over pure USB but only over thunderbolt.
This has got to be a bug on Apple's side right? Would be nice if they fixed it.
I recently tracked down some poor network performance to some dodgy Ethernet cables in my patch panel.
Since lots of comments misunderstood the article, the extra latency from going through the monitor meant his laptop couldn't acknowledge the packets quickly enough. That led a buffer on the ethernet adapter to fill and that led it to drop packets.
A different adapter which required less frequent acknowledgement fixed the problem for him.
It is quite a nice post which gets to the bottom of incredibly opaque behaviour of USB hubs.
What's the difference in BOM cost for Realtek RTL8153 (1GigE) versus RTL8156 (2.5G) versus RTL8157 (5G) versus RTL8159 (10G)?
I'm always jealous of people who have the willpower and time to investigate this kind of stuff, I would have plugged it into the laptop and moved on! It's perhaps the most nerdy "grass must be greener" luxury I can imagine (in a good way).
Nice post. Unsatisfying conclusion - did you ever figure out why the original adapter was throttled when plugged into the monitor, and not when plugged into the computer?
Would bbr congestion control help here to.get speeds to 2 Gbps?
Could this be some kind of https://en.wikipedia.org/wiki/Bufferbloat problem?
Sure we are talking about a different level in the networking stack and very different protocols. But with every component you add things get less synchronous. Well, no buffering needs to involved by the middleman, the mechanism for the throttling could also be different. What do I know...
What's your handle on Sauerbraten?
What a click-bait headline. The conclusion was that it was due to having a more bottlenecked USB-to-Ethernet adapter path. Would the same result have held with a discrete Thunderbolt 5 hub, either with a built-in 2.5 Gbps or faster Ethernet port or with the original USB-to-Ethernet adapter? Would it have held with another USB hub? Who knows -- just blame it on the expensive monitor!
> So I thought I would do what any ~~human~~ apple user would do, and I spent more money on a new adapter.
I've encountered a similar problem, the wifi on a MacBook Air was dying once connected to a Dell monitor over USB-C. The wifi signal was going from full to nearly no signal. Connecting to the same monitor with a dongle and HDMI didn't have the same outcome. Never had a time to find the culprit. Probably EMI or bad grounding.
A couple of thoughts:
1. These 1 cable solutions are nice but (IME) incredibly finnicky. I've gone through several Caldigit docks that have died;
2. When you think about it, these docks (and monitors) are really 100+ Gb/s switches. It's kind of no wonder that there are odd behaviors;
3. IME that cable that provides power to the laptop and handles power/video (you know, so it really is 1 cable) is the absolute worst. Whenever you buy them, buy 2-3 because I can almost guarantee 1 will be faulty and it'll be weird, annoying problems eg the screen gling black for a split second randomly;
4. I did a lot of testing with 1GbE USB-Ethernet adapters and it's true that they are not all created equal. In a perfect world, they should do ~930Mb/s. Depending on which one you get it'll be as low as 880 (or lower); and
5. I would honestly expect better from Apple. With the price premium you pay for these Studio monitors, I would expect the hub part to be pretty much seamless.
Hah, well if my monitor at home ever does this to me I can take my revenge by slowly removing my jacket, or sitting down on my chair. (Samsung Odyssey G9, it's ultra-sensitive to ESD anywhere near it so if I'm wearing the right jumper I can move my chair or wave my arms around and the capacitative heresy will make it wig out for a good 2-3 seconds.)
At work we run HP Z40c monitors and while they've been bulletproof in terms of image quality, on my old laptop the mouse cursor was definitely more laggy when running in a one-cable setup. We're using Logitech MX Master combos so I just moved the dongle from the monitor to my laptop and that fixed the lag issue.
Wow this sounds like a shill post. If anyone from HP or Logitech wants to talk message me. Otherwise Logitech Opti+ or whatever its called can fk off.
I hate this attitude: "I wasn’t getting three quarters of the speed I was paying for" No, you were. It was not the ISPs fault. I get constant support requests like that. People install their own equipment, adapters, wifi repeaters, sketchy unmanaged switches and keep complaining about speeds when the ONT/CPE whatever works perfectly and the connection is fine. All it takes is to connect to the CPE directly and do a measurement. It's like people calling the power plant operator directly if one of their light bulbs is dimmer than the rest.
I knew it was Apple even before clicking
I've only read the headline: USB degrading speeds?
(five minutes passed, I skimmed through TFA)
Ah yup, of course it's somehow related to USB.
It's like the infamous line: "It's always DNS" (and when it's not it's the firewall).
When download speeds are degrading like that, it's always some weird USB thing.
In the earlier days people didn't know that, for example, plugging a monitor into an USB hub could, as a result, make the rest degrade to USB 2.0 speeds. Unplug the monitor, HUB is speedy again now that it doesn't need to deal with that 4K / 60 Hz or whatever monitor data.
It's not a criticism or anything and I'm not saying that's what's going on here: I'm just saying USB has many gotchas and there can be, as in TFA and as in many other (document or not) cases, weird things happening.
At times (and doubly so when troubleshooting), you're better to simply try to plug your USB cable directly in the computer instead of in a USB hub / monitor USB hub. (EDIT: ah yup, ofc eventually he try that)
There are thing too complex to ever be secure and then there are things too complex to not have gotchas.
USB is... Wild?
P.S: and then of course in addition to this USB wildness there's the mad insanity of USB... Cables.
[dead]
[flagged]
[flagged]
This reminds me of a (completely different, but felt equally) bizzare problem with ghostty (the terminal emulator) on Linux and Steam, specifically Baldur's Gate 3.
At the start of the game after an update, BG3 compiles the (Vulkan) shaders. To avoid hammering the computer, it checks the load, including I/O pressure, and then throttles itself. It turns out that Ghostty uses io_uring, and even if it's not doing anything this somehow counts as pressure. This was made worse by the fact that I usually have a dozen or so Ghostty windows.
End result, BG3 compiles shaders using 1 core, throttled, instead of all available 20 cores. Instead of a minute or so, it'd take several hours.
(For closure: I configured ghostty to use epoll instead. Probably not optimal but works around the problem.)