The upside, though, was that I plugged it in, got my throughput, and never had to worry ever again. Remember that engineering time is mucho $$. So troubleshooting overheating, divising a solution, manufacturing it, etc, that all eats into the savings.
The $400 dock would be cool though. It seems smaller than the sonnet and fixes my charging problem. Weirdly I didn't think I'd care about not including transceivers but they did actually come in handy, so that is a downside. Might try to get one of these if I need another one in the future.
I initially read this as SONET[1] and was seriously questioning your technical choices.
[1] https://en.wikipedia.org/wiki/Synchronous_optical_networking
ConnectX-4 and newer are natively supported. I use a ConnectX-4 LX in a $50 Razer CoreX off of craigslist. Works fine, hit similar limits to what Jeff did.
Using an OCP is the neat trick here. MUCH smaller setup.
As far as the other posters comment about Tx's... that is an entirely different topic. I've never had an issue with FS.com optics personally.
If you are unfamiliar, the reality of the situation is quite bad. Slight hardware revisions of adapters/switches, which if you are lucky can be differentiated by manufacture date or serial number sequence, will not recognize known good modules, and if they do you then have to actually test if they can establish link, then let them burn for 24+ hours to see if they can maintain it without dropping (often, because of forward error correction, you will not start to see flapping until enough correctable errors have accumulated and the buffer overflows). Then there are firmware updates where this process must then be repeated.
You would think with how expensive all of this shit is you would simply be able to buy the officially listed as compatible components but my experience with them has been that a shotgun approach is best for your sanity and deadlines, buying sample kits of each module and trying them all, and then once you find the ones that play nice, buying as many of them as is reasonable and testing all of them.
If I had a dollar every time two modules from the same brand, that came in the same box, from the same production run, did not work with one another, I would be able to test your theory for free. Network Engineering is Fun
> I have SMB multichannel enabled, but this real-world speed limitation could also be related to my use of my lower-power Arm NAS (running on Ampere Altra, with 32 fairly-slow CPU cores).
Based on my own testing with a 25 Gb NIC setup on macOS I strongly suspect the issue is not on the NAS side, and the hardware I was working with is by no means underpowered.
The Mac I was working with is one of those rack mount M2 Mac Pros with a 25 Gb PCI-e card. On the NAS side it was a several hundred terabyte all NVMe flash multi-node cluster, each node with Xeon CPUs and 2x 25 Gb bonded NICs. Doing some rough throughput testing from macOS over multi-channel SMB yields throughput rates that are barely faster than the built-in 10 Gb copper NICs on the Mac.
Using iperf I can confirm that I can get near enough to 25 Gb/s raw network throughput on the Mac. And other non-macOS systems see significantly faster throughput to the same NAS. I am not sure exactly what the issue is that causes 25 Gb NICs to underperform so significantly for file sharing tasks, but I am reasonably certain that the issue is in macOS.
Atto’s new 100G Thunderlinks work well. I’ve seen speeds of just over 5 gigabytes per second. Atto definitely does a lot of kernel extension wizardry to get macOS to achieve these speeds.
A bit OT: I hope Blackmagic really shakes up the 100G connectivity market, and that Apple realizes their platform is extremely well-suited for IP Video 2110 workflows — if they can ever get networking under control.
His iperf3 results show that it's able to go full beans on a single 25g port. A cross platform SMB file copy is kind of a meaningless benchmark in this context.
IMO a pretty cool product would be a network switch providing native thunderbolt interfaces to multiple upstream hosts. That wouldn't magically fix this RDMA issue, though. This is just a separate thought. Seems like the kind of thing Mikrotik should make.
I found that SMB on macOS is just bad. If I try to heavily load it (e.g. by doing mass conversions in my Audible library), it can cause stalls and disconnections.
I managed to find a set of parameters (in /etc/nsmbd.conf) that makes it work more-or-less reliably by trial-and-error: dir_cache_off=yes, file_ids_off=yes, notify_off=yes, mc_on=no.
It's still terrible, though. It's so bad that Linux in a Parallels VM works _better_.
MacOS has supported RDMA over thunderbolt since March 19th.
See also NVMe drives? They draw enough idle power to drain a laptop battery overnight, and will easily hit 60+C in a bad enclosure. That’s only a 10Gbps module. The USB4 enclosures are all heatsink.
And your computer already speaks the PCIe and thunderbolt. It has that probably on CPU. Here we have to receive USB, convert it to Ethernet. On much less up to date process nodes than your CPU.
Third, until very recently for even 10Gbit it meant using a usb4<->pcie bridge chip which itself was hot, to provide a generic pcie connection, which then talked to a conventional network chip, so it was a double hop: USB <-> pcie <-> nic. I don't know if 25Gbit to USB direct convert is available yet but we've seen a wave of vastly cheaper 10Gbit adapters come out that are single chip USB<->nic, probably not pcie at all, that are much much cooler. 25Gbit is probably still not here yet, maybe?
With ethernet it's for lots of reasons but a big one is not creating ground loops between distant equipment. If you didn't isolate the network cable would be sinking potentially amps of current between distant devices and that just isn't sustainable. You don't have this problem attaching USB between two devices.
The NIC in this setup was released 12 years ago. It's built on a very old process.
you can look up the rated power use of a connectx4 card, they do a lot of offloaded computation, too
> this real-world speed limitation could also be related to my use of my lower-power Arm NAS (running on Ampere Altra, with 32 fairly-slow CPU cores). I was testing writing to an array of fast enterprise NVMe SSDs, so they shouldn't be the bottleneck here.
He was only getting 1 Gigabyte of throughput out of the built in 10 Gigabit Ethernet connection and moving to the 25 Gigabit connection only made a marginal impact on throughput, after all.
So for instance you have two or more machines that have USB 4 ports at 20 to 80 Gbps and you plug in the appropriate USB C cables to connect them.
What do you need to make the connections appear as a (point to point) part of a regular TCP/IP network? Seems much cheaper than Ethernet if you already have the ports.
I believe MacOS supports it via the usual network control panel. I’ve used it for transferring data from an older laptop to a newer one. The cable is more expensive than fiber, last time I checked.
Latency was an order of magnitude higher than twisted pair but the throughput was greater than 10Gbps and I didn’t have to spend on 10GbE capable servers and network equipment. I vaguely remember that they had to be proper Thunderbolt not just USB-C but that could have changed it’s been quite a while.
But for all certified Thunderbolt 4 and 5 ports, this kind of networking support is a requirement. (It is optional with Thunderbolt 3.)
The rest is up to the operating system.
Plugable 2.5G USB-C to ethernet adapter (bought November 2025), SABRENT USB C to 2.5Gbps ethernet adapter (bought October 2024), UGREEN USB C 2.5G ethernet adapter (also October 2024). In my experience they immediately fall on their face in a speedtest and drop to a couple hundred Mbps, experience packet loss, etc. This is testing across a few modern Apple Silicon Macs.
I now have a WavLink WL-NWU341G 5Gbps dongle with the RTL-8157 that seems to work well, but I've only run a couple of tests-- I am away from my home setup and don't have wired ethernet run to all the rooms where I'm living.
If you do some Googling, there's some good information out there about it, but when I bought the bad ones, I couldn't find any information corroborating my experience.
On a CalDigit TS3 dock, I've had one working off the rear Thunderbolt socket for over a year, but it fails in minutes if plugged into the USB-C one. I've never had issues with a CalDigit Elements (TB4) hub. I've had success plugging them directly into various Chromebooks. On one Windows laptop, they seemed to work on one USB-C port but not the other.
So... reliable once working, but getting there can be a pain.
Nothing against Jeff Geerling and I love his YouTube channel and I'm glad he's one of us HNer but this crop of circular "I make YouTube vids about big tx speeds and big NAS because I make vids hence I need big tx speeds and big NAS so I can speak about big tx speeds and big NAS because I make YouTube vids about big tx speeds and big NAS" videos is a bit tiring IMO.
I'm not into cryptocurrencies but, I don't know, host a full Ethereum node, host a Plex/Jellyfin server serving thousands of movies, host LLMs, etc.
I mean: talk about something else than editing vids because you make vids about vids.
Author talks about 4k video, but AI tells me that for "4K production mastering (ProRes 422 HQ, 4:2:2, 10-bit)" the rate is under 2Gbps.
I'm not saying it's not needed, - just curious.