My monitor was cutting my download speed by 75%
blog.tymscar.comIt's explicitly not a bandwidth issue (that would also affect the SSD). It's a latency issue - the chip doesn't have a big enough buffer to keep sufficient packets in flight at once.
That's explicitly the opposite of what the author says.
"the speed of packets coming into the adapter is 2.5 Gbps. That’s what the router pushes in. The speed going out is around 2 Gbps."
Of course latency is always on the denominator side in the "bandwidth = data / time" equation, but it seems wrong to claim it's latency when it could also be improved by fixing the numerator; it's the entire fraction that's insufficient, thus bandwidth. As written:
"The reason is that if you add up the average time it takes to get the go-ahead through my monitor’s hub, which is around 7.6 µs, to the average time it takes to send 4 KB, around 8.2 µs, you can find what the maximum speed is"
And later, increasing the numerator is exactly what fixes it with the other hardware: "I can see that instead of sending 4 1 KB packets per burst, it would send 8!"
> the chip doesn't have a big enough buffer to keep sufficient packets in flight at once
How does this make sense? Even if his buffer was 100x larger, if the fill bandwidth exceeds the drain bandwidth, it'll eventually fill up. The article says that explicitly:
"Well, if the speed of the drain from my adapter to my Mac is half a gig slower than the speed of the input, then you can imagine the buffer getting filled more and more until it overflows."
"buffer" was perhaps a poor choice of words on my part, because "buffer" is ambiguous. In this case I am referring to the notional "transmit buffer", which is 4 in the non-working case and raised to 8 in the working adapter.
> "I can see that instead of sending 4 1 KB packets per burst, it would send 8!"
Increasing the number of packets in flight does not change the bandwidth, it only improves latency sensitivity (i.e. you can fire more data before requiring an ACK).
> it seems wrong to claim it's latency when it could also be improved by fixing the numerator.
Increasing the bandwidth without increasing the transmit buffer would not fix this issue. The adapter he ends up buying does both (allow 2x the packets in flight, and 2x the bandwidth).
The bottom line here is that the original adapter handles full duplex 2.5g when plugged into the laptop directly, and the SSD gets full duplex bandwidth in excess of 2.5g through the same intermediate link (i.e. the display), so both the adapter and the display have sufficient bandwidth. The added hop of latency however makes the short transmit buffer insufficient to cover the latency.
Then I agree with what you were saying. Those 4 * 1 KiB are a protocol-level size (similar to the TCP window size), not an actual "buffer".
> Increasing the number of packets in flight does not change the bandwidth, it only improves latency sensitivity (i.e. you can fire more data before requiring an ACK).
That I don't fully follow. To me, the measured bandwidth includes all the effects of ACKs etc. If the the protocol demands that you can have at max 4 * 1 KiB unACKed in flight so you're waiting around for ACKs and not snding data, then increasing the number of packets in flight to 8 would 2x the bandwidth.
> The added hop of latency however makes [it] insufficient to cover the latency.
I agree with that, see also my newer reply https://news.ycombinator.com/item?id=50592931
I this context, I also agree with your original statement; I misunderstood what you referring to with "buffer" (meaning the window, not actual storage), and "bandwidth" (where I think you're referring to the 5 Gbit/s nominal bandwidth of the bus, irrespective of the fact that the effective bandwidth of data sent is much lower due to requiring ACKs for small data).
The latency added in the monitor is described as around 8 us, completely negligible compared to any Internet connection's latency.
So the latency without the monitor should be completely irrelevant.
I thought their "latency without the monitor" had referred to the overall end-to-end connection to the other IP endpoint, but they were talking about `NIC <-USB-> laptop`.
This part is saying the NIC with this monitor can transfer 4 KB to the host through the USB hub every 15.8 us. You can do the math and it's about 2gbps.
Remove the hub, and reduce the delay solves the problem.
Increase the burst size would work: 8 KB per 24.0 us would be sufficient for 2.5 gbps.
Increase the burst size and the transfer rate as done with the 5 gbps adapter, and that should work out, although that one is probably going to be insufficient for full rate 5 gbps as well.
"if the speed of the drain from my adapter to my Mac is half a gig slower than the speed of the input, then you can imagine the buffer getting filled more and more until it overflows. Those are dropped packets, which result in a hard backoff when the router resends them, so you drop loads in speed. And that’s the reason for all of this."
With diagram https://blog.tymscar.com/studio-display-ethernet/bottleneck....
The monitor decides to send the adapter's packets on at only 2 Gbit/s, which leads to buffer overflow, thus packet loss, thus e.g. TCP congestion-control backoff.
The only thing we don't know is _why_ the monitor chooses to limit the bandwidth to those 2.07 Gbit/s (computed as the 41 KiB blocks per (7.6+8.2) µs). If it sent e.g. 81 KiB blocks, doubling the bandwidth, the problem wouldn't happen.
That'd be between Apple and the monitor.
The monitor was not really at fault. All USB hubs must read USB packets on all of their ports and copy them over to the upstream port. Those packets must all go into a buffer first so they the hub can send them individually even when they arrive simultaneously. That introduced just enough delay to allow the NIC’s internal buffer to fill up. Any hub would have caused the same problem. The solution was to buy a NIC designed for a higher speed because it has a bigger internal buffer. That new NIC will probably have the same problem with USB hubs, but at 5Gbps instead of 2.5Gbps.
It’s really the NIC’s fault because its buffer is too small to handle a little extra latency.
Where does the "4" come from? The article's diagram suggests that the NIC's buffer is "~35 KB", though I don't know where that number comes from either (I supposed measuring how long it takes until frames are dropped). "4" seems to be the number of 1 KB packets (the 3+1 from "packet size 1024 bMaxBurst 3"), so a transmission size (protocol-level "window size"), not a buffer size. I guess if you are referring to that as a different "buffer", that makes sense, but it doesn't seem to be the buffer the article is talking about.
But you are right with your main point regarding latency. My statement
> The monitor decides to send the adapter's packets on at only 2 Gbit/s
isn't really right: It's not that the monitor "decided" to only send 41 KiB instead of larger sizes; the 41 KiB is the maximum that the NIC can send because its `bMaxBurst = 3`, and the latency added by the monitor being a USB hub then limits the bandwidth to the mentioned ~2 Gbit/s.
I guess the key point not said anywhere is that `bMaxBurst = 3` and `wMaxPacketSize = 1024 B` are fixed protocol-level parameters that hubs like the monitor have no control over. So the 4 KiB windows are fixed from the NIC through the monitor to the Mac; the monitor cannot e.g. decide to buffer some of those to compensate for the latency it adds.
computed as the 4*1 KiB blocks per (7.6+8.2) µs). If it sent e.g. 8*1 KiB blocks
not computed as the 41 KiB blocks per (7.6+8.2) µs). If it sent e.g. 81 KiB blocksSure 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...
The 35 KiB buffer from the article is not very large, and the problem would exist unmodified if it was smaller.
As the article explains, "if the speed of the drain from my adapter to my Mac is half a gig slower than the speed of the input, then you can imagine the buffer getting filled more and more until it overflows", and this would hold for any buffer, smaller or larger.
Bufferbloat causes primarily latency problems, not bandwidth problems.
Bandwidth problem would occur at most as secondary effects, e.g. if a packet is delayed by a buffer for so long that the sender-expected timeout for an ACK expires, it considers the packet lost, and throttles down sending. But that's not happening here.
It's unreasonable assumption to expect such a setup to manage multiple full speed connects in my opinion.
If I was running support it and later heard on I just unplugged the ethernet from my monitor direct to my laptop and the speed improved I'd dispair.
The bandwidth in question is nowhere near saturating even a single USB3 connection.
It's a lot easier to hit real world limits than theoretical spec limits.
Edited to add: Unlike networks in general, the USB standard imposes maximum diameters and latencies, so designers know what to design for. If the higher-spec adapter also had awful goodput, then it might be reasonable to point fingers at the monitor.
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.)
Especially for something like compiling shaders. It literally never happens unless the user is about to go play a game, which is going to consume most resources anyway. To the user, there's nothing more important running right now.
Well, to a certain degree. I have a relatively uncommon GPU, and run games on Steam (and Linux), so literally every game does shader compilation for me. Even with a beefy CPU and beefy GPU, if the shader compilation uses more than 16 threads, my computer basically freezes until its done with it, as it's so performance intensive, kind of have to throttle things if I want to be able to use the desktop for the 10 minutes the shader compilation takes sometimes.
Edit: "Do you use Linux? That only happened to me when I was using a dram-less ssd for swap and doing IO heavy operations on the NFS mounted drive"
I do! I do have NFS drives, but not for Steam games or anything else relevant. I'm also not using swap at all. RAM seems fine during this, it's just pegging all cores to 100% usage immediately and stays there, making everything else suffer.
Sounds like a scheduling problem that should be adressed at the OS level.
1. Have you tried enabling full preemption as well? I run Debian, and before I did that I had lots of stutters from any kind of background load thanks to dynamic preemption.
2. Even then, ZFS was causing stutters until I lowered it's priority as well (spl_taskq_thread_priority=0)
3. On non-ZFS drives, try setting your I/O scheduler to Kyber for NVME or BFQ for everything else. "mq-deadline" isn't great for interactive use on a SATA SSD, even for non-boot drives, and even NVME sometimes stutters under "none" for some people.
> I'm also not using swap at all.
4. zswap (combined with zstd compression, "min_ttl_ms=1000", and "vm.page-cluster=0") and "defer+madvise" memory compaction can help. (Something about the kernel really liking having swap on-hand.)
Steam runs shader compilations at batch policy and nice 19, so without RAM or I/O bottlnecks even gaming shouldn't be too bad (though from personal experience it still induces some stuttering). It's just most distros are tuned horribly for this. (Not to sound flippant, I understand the frustration of "just try this" and it doesn't work, but it's everything I can think of RN.)
But it's also possible that the problem is in the kernel and the shaders are actually doing some system call that's locking up the kernel. Like maybe there's a bug in your cuda or nvidia driver that's causing the kernel to lock.
Strange. This never happens to me on Windows. I only notice that the fans spin up a little because all cores are pegged.
You in particular should probably disable a couple cores until your hardware stops being defective. Have you looked into updates and voltage droop compensation settings?
If they want to cater to customers who foolishly reject reality and take every claim from manufacturer’s at face value… then foolishly misaimed blaming seems expected?
But if they just roll over and swallow the foolish blaming without even challenging customers to double check, then they are also facilitating more nonsense.
Users can be unreasonable, but in this case I agree - if I reported an issue to a vendor and their response was "return your motherboard" I wouldn't work with that vendor again.
> I wouldn't work with that vendor again.
Possibly rightly so, if it's bad motherboard hardware. Could also be a bad power supply, bad ram, bad CPU, user misconfiguration, etc. It's a complex system, where everything has to NOT be bad for it to be deterministic.
There's a necessary level of competence required with self built systems, or any other task in human life that you're not paying someone else to do for you. That's fine. Go buy a MacBook or a pre built system if that threshold of competence can't be met. That's why they exist, for people that can't or don't want to bother.
You're examples are flawed. Those are to safely halt operation on failure. What you're suggesting with the software is to limp along pretending everything is ok.
The proper test, more in line with your others, would be to catch failure and halt operation. Since, in your case c the human isn't competent enough for that, it would maybe be a self test initiated by the operating system, then a refusal to continue when the hardware problem is identified, emulating all the periodic inspections that are part of all the proper operation of all the physical systems your mentioned.
I think the elevator analogy to this bug is that the elevator goes too fast and triggers the brakes if you input target floors more than 8 apart. You don't fix that by having the user or user software be more careful about button placement, you fix the hardware/firmware.
Why not just re-nice the process or whatever equivalent for the threads that do the compiling? Tell the kernel what’s going on, it will handle it for you.
Don’t hack your own solution.
It looked at fossilize code (open source component used in the process), found a couple of threads online that suggested io_uring/iowait and told me first to try closing the ghostty windows and then to try to switch to epoll. This did the trick.
I have a very vague understanding of what's going on (actually better now that I've look at the links/resources from the replies in this thread!), and would probably have been able to figure it by googling in my own. But, my first hunch was that it's a problem with steam, proton, or the game, so I'd probably waste a lot of time in that direction first.
If I am reading the thread correctly, the io_uring maintainer's position is that applications trying to use the metric that "poll via io_uring" handles differently from "poll via epoll or select" are fundamentally misguided and measuring something that doesn't make sense, so they don't want to slow down io_uring to placate those apps.
> iowait is fundamentally incompatible with sane accounting in the first place, that is the problem. It really tells you nothing, and was deprecated since the days of uniprocessor systems. The problem here is not how iowait is done in the kernel, it's that people are using this metric in the first place. Which is why you just want to NOT do that, and do sane accounting on your disk drives, if you care about that kind of thing.
> Which is why I refuse to cater to any kind of iowait accounting metrics, it's just adding overhead to support a metric that is largely nonsensical in the first place. It doesn't answer any questions that an application/tier owner would want to know. Those questions might be things like "am I I/O bound?" or "is the device I'm using being slow?". I wish people would realize that, rather than continue to place value in iowait as a metric for ANYTHING, and stop trying to work around it.
It sounds more like their position is "iowait is a useless metric" and that polling with io_uring completely breaks iowait metrics but fixing it would add a minor slowdown so they refuse to do so because they don't think it's a valuable metric to begin with.
Also if you're running untrusted code that attacks your not-very-common terminal emulator, you're probably in more danger from the "untrusted code" part. Threat model and all that stuff.
(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.
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.
Well yours seems pretty great!
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 have had hundreds of USB devices in the past which dont work on a USB hub, its very common. The first troubleshooting step in basically any USB devices manual is if you are having trouble and you are using a hub, remove the hub and plug directly into the device.
The user went way over the top in troubleshooting this issue. Thats the first thing I would have tried. Its not worth the post and the title should really be something like "USB device didnt work with a hub, but did directly in the host" and it would never have made it to the front page of HN other than maybe to be mocked.
I am saying your blame is misplaced, and that the adapter manufacturer deserves the blame because they designed their product around a controller whose USB implementation has so much inherent latency that it mathematically cannot sustain the product’s advertised throughput when connected through a hub. The manufacturer should have tested this extremely common scenario and picked a part that could sustain it.
> The manufacturer should have tested this extremely common scenario and picked a part that could sustain it.
Hard disagree. Maybe if you bought a better one you would expect that, but I would expect a $15 2.5Gb ethernet adapter to not work on a hub right off the bat tbh.
None of the parts are broken. Together they don’t work as they are supposed to because of some super intricate process of how usb works when it comes to acknowledging packages. That’s why I wrote the post. The title is true and yeah, it’s sensational but that’s what titles are there for. It’s not a false clickbait.
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
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".
The root of all evil right there. ;)
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.
> 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): much celebration with V.32/V.90), 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 (and not just a momentary spike on patch Tuesday)?
Even better is those can saturate as much bandwidth as possible while the rest of the family are uninterrupted with Netflix or video calls.
Run it in background, don’t update so often perhaps; I guess I just update as tic.
I think going from something like 100 Mb download to 1 Gb is slightly overrated. You hit heavy diminishing returns. Symmetric Upload, for me, is what really changes your quality of life a lot. Uploading a youtube video suddenly isn't an event, it takes a few seconds. Want to upload an image in any chat? Done before you consciously see it uploading. Heavy commits are instant, even with a bunch of resources. It changed my behavior. I started uploading more stuff to remote servers because the cost in time got so much lower.
Let's say you're on a Meet call with a dozen of people, one of them presenting their screen to explain an ongoing incident. You're following along while checking your dashboards and code on a remote server. You're of course keeping Slack sessions in the background.
I don't think you'd be saturating a 2.5G bandwidth, but perhaps about half of it ?
If your family is also using it in parallel that could get close to full use.
This is closer to 1-10Mbps than 2.5Gbps. Slack is negligible bandwidth. Video conferencing is high compression, low bandwidth video.
The 1G and 2.5G lines benefit bulk file downloads.
I have been on Zoom and Google Meets calls with that many people on my laptop which has a Wifi connection of ≤400 Mbps (sometimes <200Mbps). You don't need >500 Mbps for online meetings.
Are you in meetings where everyone is sending 4Kp60?
lowres, please.
only 4K if the feed is from a full room with +10 people in it.
Where I work, group call participants send about ~1Mbps of video, and maybe more for screen share, could be ~2Mbps.
So you're looking at 15 Mbps inbound and 1 Mbps outbound for the call. Plus some overhead for congestion control. That's not even 1% of your 2.5gbps connection. IIRC Meet uses higher limits, so maybe double it to 30 Mbps.
You don't need gigabit for video conferencing, unless you're running the conference out of your house. Or you have 20 people all on conferences. You may want some QoS if your usage is near your bandwidth limits. Conferencing is sensitive to jitter and loss.
At my current ISP, speed is either 100M or 1G, so if you had 3+ people who conference simultaneously, 100M might well be limiting, so you would probably want 1G ... otoh, conferencing is usually bandwidth adaptive too, so it would still work, as long as everything plays nice with congestion.
An interesting side effect is that bufferbloat becomes less of a problem - you’re more likely able to pull 1gbps without spiking your ping.
But to be honest unless you have a household with multiple people, it’s something you mainly notice occasionally with updates, backups, large assets, etc.
Fetching from Google or anything on S3 can definitely fill your pipe
It’s great when experimenting with LLMs because I can quickly try new models and download from the internet almost as fast as if coming from my NAS.
Game updates are also a great use case. I don’t game often so when my friends want to play I often have to update the game. Some patches are 60GB or more. When they come down at full line speed that’s valuable time I’m getting back to spend with my friends in game.
This also locks me out of hosting my own “cloud” storage at home where it belongs - I don’t want to be out and waiting forever to get a file, so I stick to traditional cloud services for now. Slower than local storage on the LAN of course though.
A fiber isp is digging trenches soon. Cannot wait!
Yeah definitely Linux ISOs. It's nice to settledown in an evening, pick a new Linux ISO I haven't used yet, and veg on the sofa watching it install.
Of course unlike the netinstall images all the normies use, you have to download it up front before you start wa, uhm, installing it. But I prefer it that way so I can watch the install without being interrupted... Then again I guess at 2.5Gbit the only thing that's going to interrupt you is a crappy integrated network interface, aka Apple monitor. I don't have enough money to have that problem though.
But I run servers at home and regularly download enormous video files so I can think of plenty of ways to max out a 2.5 Gbps connection (alas my own is nowhere near as fast).
The benefits are two-fold:
1. Background tasks don't impact your own issue (as you say).
2. Many CDNs can saturate 4 Gbps, so if you download something, the waiting time is much shorter than say 100Mbps.
Whether it's worth it all depends on the price difference.
4Gbit is kind of the sweet spot currently. 2.5Gbit equipment became quite cheap (e.g. Ubiquiti Flex Mini 2.5Gbit managed switches are often around 50 Euro), existing Cat 5e cabling still works reliably, and if you have a router with 10Gbit upstream and multiple 2.5Gbit downstream ports, none of the subnets can completely saturate the upstream bandwidth.
Also, these bandwidths rock for doing an initial backup, downloading a full backup, pulling many Docker images, large and frequent NixOS rebuilds (unstable-small, yay). Downloading GTA 6 (not me though, not a gamer).
I don't know what you have in mind regarding what qualifies as residential usecases. I can tell you that I use my residence for work, and as part of my work I have to hold video calls and download all kinds of packages from the internet, including pulling container images, including media asset bundles that take several GB.
This often takes place when other members of my household are doing their work or watching streaming services.
If you have a 2.5Gbps connection, you often are not looking into sustainable transfer rates but bursts. A difference between 500Mbps and 2.5Gbps is whether it takes you half a minute to pull a package or 5-10 minutes.
I only upgraded because my isp charged $90 for 1gig and offered 5 gig at $65 for two years so for the price of a pci nic I thought why not. It’s also nice that every device in the house can max out their capability simultaneously but that’s a rare event.
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.
All the more irritating is that all this dock and dongle bullshit was popularlized by them.
The fact that it's a monitor is a little bit irrelevant.
The fix is to cut the overhead by sending more than 4 frames per interrupt. Unfortunately that required buying a new adapter with a different chip.
So it certainly seems possible to have an additional device in the signal path.
I think I'd have accepted having two cables from the get-go. And if I observed this problem, the first diagnostic I would do is to plug the Ethernet directly into the laptop.
Fewer technical pieces in a puzzle sometimes trumps ease of use.
To pick a not-RAID example, I've got an old (2012-vintage) 180GB SATA SSD, from Intel, on my desk. It gets used as scratch space for big-ish file operations, where it gets hammered hard periodically, usually in bursts. It's plugged into a cheap SATA <> USB 3 adapter, and is otherwise-unadorned. It is bus-powered.
It's usually connected to the back of the PC, but it's been plugged into different USB ports (with different controller types) and also external hubs.
I don't recall what its exact status was when I starting doing that with it after pulling it out of a gently-used Thinkpad T530 about 5 years ago, but I do recall thinking that it had lots of life left.
Here's where it is today:
- 10.6 years powered on
- 81TB written (of 36.5TB promised); ~222% over spec
- Zero reallocated sectors
- One singular hardware-reported error (corrected)
- Zero sector reallocations
And the pièce de résistance: - Zero reported errors according to ZFS checksums
That last one is important because in this application, ZFS automatically and continuously provides end-to-end verification, and it's been doing...perfectly fine.The other USB storage devices here that are used 24/7 are similar in this way. It's not hellish at all. It's quite lovely.
I'm inclined to further extrapolate that it would not have better data integrity when connected directly to a SATA port on the motherboard, or in a disk shelf attached via iSCSI or SAS or some other more-stodgy thing. It's hard get results that exceed beyond perfection.
(But in this example, I'm not chasing down minute bus timing issues with multi-gig networks. That's a very different kind of discussion.)
I understand that not everybody likes this, because it can feel like a trick, or patronizing, or lying. But in my experience, it works very well for people.
Now I feel as though my time was wasted by a dishonest author trying to get me to believe that their story was interesting when it was not.
In the grand scheme of things, it’s not a very big deal, but I feel quite annoyed since I was baited into expecting a fun read.
This was super surprising, have always thought ISPs are a super hard businesses. But good for you mate, good ISPs are lifesavers.
I have had the opposite experience with my ISP guys. One of the VMs I got as part of work only had IPv6 and to my shock my internet didn't have one. When I contacted my ISP they legit told "You can either have IPv4 or IPv6, but not both". Unfortunately I was on a 12 month plan and couldn't easily cancel so ended up working around using tailscale.
This would reduce the established connection speed due to electrical noise from the monitor.
Anyway, the exact same situation arises, where some network condition or physical configuration (there’s a lot of hardware in between these two devices, including MoCA adapters) meant that the network adapter buffer fills up and starts dropping packets. The buffer size is configurable through some terminal command and maxing that out makes the issue disappear immediately.
Weird. It's the first time I hear someone has a cupboard of those. Everyone I know keeps them in a drawer.
[1] https://www.speedrun.com/Pragma_Twice
[2] https://developer.mozilla.org/en-US/docs/Web/API/Window/requ...
Immediately 10X'd my bandwidth, turned out I was using a cheap cable that wasn't shielded like it was supposed to be, and it was running right past the WiFi antenna and causing loads of interference.
Actually, the speed of gigabit Ethernet adapters are also known to cut 60% behind a studio display. TBH I assumed it was because USB ECM sucks and NCM (which RTL8156 implements) was supposed to fix it.
One thing that can happen with pause frames (and why I hate them) is pause propagation. If you have a switch between your server and client and the client sends the switch a pause frame, the switch may send a pause frame to the server. If it does (and the server accepts pause frames), the server will pause sending to all destinations.
So your one slow client can disrupt all the other flows from the server. Which is totally unhinged.
These tend to not support sending pause frames to its SFP+ side either, so the best option I found was to set bandwidth limit on the NIC…