What 10GbE actually fixes

Gigabit Ethernet caps out around 118 MB/s in the real world, after protocol overhead. That’s fine for streaming media, browsing, and most day-to-day traffic, but it becomes the ceiling the moment you’re moving large amounts of data between two points on your own network - copying a media library to a new NAS, restoring a big Proxmox Backup Server snapshot, or running a VM off networked storage (iSCSI, NFS, or an SMB share) where every read and write crosses the wire.

10GbE raises that ceiling to a theoretical 1.16 GB/s, and in practice you’ll usually see 400-900 MB/s depending on the drives and protocol on each end, since the network stops being the bottleneck and something else (usually the storage itself) becomes the new limit. That’s the real payoff: it moves the bottleneck from “the network” to “whatever’s actually slow,” which is often spinning disks, a single SATA SSD, or the CPU doing checksum/encryption work.

Where it’s a clear, obvious win

NAS-to-client bulk transfers. If you regularly move tens or hundreds of gigabytes between a workstation and a NAS (media libraries, VM images, large backup sets), gigabit is the wall you keep hitting. This is the single most common and most justified reason homelabbers upgrade, and it’s usually the first place people notice the difference immediately - a transfer that took 20 minutes on gigabit finishing in 2-3 minutes.

Networked storage backing live VMs or containers. If you run Proxmox with storage on a separate NAS over iSCSI or NFS rather than local disk, gigabit’s latency and throughput ceiling shows up as sluggish VM boot times, slow snapshot operations, and I/O wait under any real load. This is a case where 10GbE isn’t just about bulk transfer speed, it’s about the storage backend feeling responsive at all.

Backup windows that are currently network-bound. If a Proxmox Backup Server job or a NAS-to-NAS sync is taking hours and CPU/disk usage on both ends looks idle during that time, the network is very likely the actual constraint, and 10GbE will show up directly as a shorter backup window.

Multiple simultaneous users or services hitting the same storage. A single gigabit link gets saturated fast once more than one device is pulling from the same NAS at once - a media server streaming to two rooms while a backup job runs in the background, for instance. 10GbE gives you headroom that gigabit just doesn’t have to share.

Where it won’t move the needle

Internet-bound traffic. Your actual internet connection is almost certainly nowhere near a gigabit, let alone 10 gigabit, so upgrading internal networking does nothing for anything that touches the WAN - streaming from an external service, downloading, or remote access speeds. This one trips people up constantly: 10GbE is for traffic that stays inside your own network.

Storage that can’t saturate gigabit in the first place. If the NAS on the other end is running a couple of spinning HDDs in a basic array, you may already be capped well under 118 MB/s by the drives themselves, especially on random I/O rather than big sequential transfers. Upgrading the network in that case buys you nothing until the storage is upgraded too - check your actual sustained transfer speed against drive-rated throughput before assuming the network is the limiter.

Single-client, occasional-use setups. If your “network load” is one person occasionally copying a folder of photos or pulling a single stream, gigabit was never the bottleneck to begin with. The upgrade is real money and real effort for a problem you don’t have.

Wi-Fi-bound clients. 10GbE only helps the wired segment. If the actual client doing the transfer is on Wi-Fi, you’re capped by the wireless link’s real-world throughput long before you’re anywhere near gigabit, and 10GbE on the wired side changes nothing for that device.

What it actually costs

The used-enterprise-gear math applies here just like it does for servers (see the earlier hardware piece on buying used enterprise gear): a used managed switch with SFP+ ports is one of the best value plays in networking, but check fan noise before buying one that’ll live somewhere you can hear it.

Switches. A basic unmanaged 4-8 port SFP+ switch is the cheapest entry point if you just need to link a couple of machines directly. A managed switch with real 10GbE port density (Cisco, Juniper, Ubiquiti, MikroTik) costs more but gives you VLANs, LACP, and room to grow - worth it if you’re already running VLANs elsewhere in the network.

NICs. Used enterprise 10GbE NICs (Intel X520/X540, Mellanox ConnectX-3) are inexpensive on the secondhand market and well supported in Linux and Proxmox out of the box. Consumer motherboards essentially never ship with 10GbE built in, so plan on adding a card to anything that isn’t already server-class hardware.

Cabling. This is where people overspend without meaning to. SFP+ direct-attach copper (DAC) cables are the cheapest option for short runs (under 3-5 meters, machine-to-switch or machine-to-machine) and need no separate transceivers. For longer runs, or 10GBase-T over existing Cat6/Cat6a copper, you’ll need RJ45-based 10GbE NICs and switch ports instead, which run hotter and cost more than SFP+ gear at the same speed. If your machines are physically close together, SFP+ DAC is almost always the cheaper, simpler answer.

Power and heat. 10GBase-T (RJ45) ports run noticeably warmer than SFP+ optical or DAC ports, on both switches and NICs. If you’re switch-shopping for something that’ll sit in a closet with poor airflow, SFP+-only or SFP+-heavy switches tend to run cooler and quieter than switches full of 10GBase-T ports pushed to their rated distance.

A simple way to decide

Before buying anything, do the actual math on what you’re waiting on today. Time a real transfer between the two points that would benefit most (workstation to NAS is the usual candidate), and check whether it’s hitting anywhere close to gigabit’s real-world ceiling (100+ MB/s sustained) or well under it. If you’re already well under gigabit’s ceiling, the bottleneck lives somewhere else (usually spinning disks or a slow protocol/config on the storage side) and 10GbE won’t fix it until that’s addressed too. If you’re consistently pegged at the gigabit ceiling and it’s actually costing you time you care about, that’s the case where 10GbE pays for itself in convenience alone, even before counting the used-market prices that make it one of the more approachable upgrades in this hobby.