Why Your NAS Transfers Are Slow: Network Speed Bottlenecks Explained

Your NAS is supposed to deliver fast, seamless file transfers. Instead, you’re getting 40MB/s when you expected 100+MB/s, or copies to the NAS crawl while reads are faster, or speed varies wildly depending on file size. Understanding where the bottleneck actually is — not where you assume it is — is the difference between an effective fix and an expensive upgrade that changes nothing.

Table of Contents

The Speed Ceiling Hierarchy

Network storage speed is limited by the slowest link in a chain of potential bottlenecks. In order of how commonly each limits real-world transfers:

Network interface (most common): Standard gigabit Ethernet (1GbE) has a theoretical maximum of 125 MB/s. After protocol overhead, real-world throughput is 90–115 MB/s. If you’re getting 90–115 MB/s, gigabit is your ceiling — not a problem, just physics.
Wi-Fi: Even Wi-Fi 6 in ideal conditions delivers 200–600 MB/s theoretical — but that’s shared bandwidth, half-duplex, and sensitive to interference. Real-world single-device Wi-Fi NAS transfers typically max out at 40–80 MB/s on good connections, 10–25 MB/s on weak signals.
Drive write speed: Your NAS drives’ write speed, combined with any RAID overhead. A single spinning HDD writes at 100–200 MB/s. In RAID 5, parity calculation can reduce effective write speeds to 60–150 MB/s depending on the RAID controller’s CPU.
NAS CPU: Older or underpowered NAS CPUs (like Synology’s J-series Realtek chips) can bottleneck at 50–80 MB/s for SMB transfers due to encryption or protocol processing overhead. N100 mini PCs don’t have this problem.
Switch quality: Unmanaged switches occasionally introduce latency or duplex mismatch issues. Usually not a bottleneck, but worth checking if all else is fine.
Client storage speed: Reading from your NAS and writing to a slow client drive (old spinning HDD, USB 2.0 drive) can make the NAS appear slow when the client is actually the bottleneck.

Diagnosing Your Specific Bottleneck

Test 1: Network Connection Speed

Open a terminal or command prompt on your NAS (or in TrueNAS’s shell) and run an iperf3 test between the NAS and a computer. On the NAS: iperf3 -s. On your computer: iperf3 -c [NAS-IP]. This tests raw network throughput between devices, bypassing drives and file system overhead.

If you get 900–940 Mbps (about 112–117 MB/s): your network is healthy at gigabit. The ceiling is the network itself.
If you get 300–700 Mbps: possible duplex mismatch, a cable issue, or a failing NIC. Try replacing the Ethernet cable first.
If you get under 100 Mbps over wired Ethernet: significant network problem requiring investigation.

Test 2: Drive Speed Independent of Network

On your NAS, run a direct read/write test to the drives using dd on Linux:

dd if=/dev/zero of=/mnt/your-pool/testfile bs=1G count=10 oflag=direct
dd if=/mnt/your-pool/testfile of=/dev/null bs=1G count=10 iflag=direct

This bypasses network and tests drive write/read speed directly. If this is fast (100+ MB/s) but network transfers are slow, the bottleneck is network-side. If this is slow, you have a drive or RAID performance issue.

The 2.5G Ethernet Upgrade: When It Actually Helps

2.5 Gigabit Ethernet (2.5GbE) offers 312 MB/s theoretical throughput — 2.5x faster than standard gigabit. Many mini PCs (including most N100 machines and essentially all Ryzen-based mini PCs) already include a 2.5GbE port. However, upgrading to 2.5GbE only helps if:

Your current transfers are actually hitting the gigabit ceiling (90–115 MB/s)
Your router or switch also has 2.5GbE ports (most consumer routers don’t — they typically have 1GbE LAN ports)
Your client machines also have 2.5GbE ports

If your transfers top out at 40–60 MB/s, adding 2.5GbE changes nothing — something else is the bottleneck. The most common scenarios where 2.5GbE provides real benefit: transferring 4K video files between a 2.5GbE-capable NAS and a 2.5GbE-capable desktop over a 2.5GbE switch.

SMB Protocol Configuration Matters

The SMB protocol version and settings significantly affect NAS transfer speed. SMB 3.x with multi-channel enabled can improve throughput when both client and server support it. In TrueNAS: Shares → Windows (SMB) → enable “Allow SMB2/3 Multichannel” if available. On Windows: Set-SmbClientConfiguration -EnableMultichannel $True in PowerShell (run as administrator).

For Linux clients using NFS instead of SMB, NFS typically achieves 10–20% better throughput than SMB at the same network speed for large file transfers — worth considering if your main NAS clients are Linux machines.

Small File Transfers: Why They’re Always Slower

Transferring 10,000 small files (photos, documents) is dramatically slower than transferring one 10GB file of equivalent total size. This isn’t a NAS problem — it’s fundamental to how storage and network protocols work. Each small file requires separate metadata operations, protocol round-trips, and disk seeks. A folder of 10,000 JPEGs might transfer at 5–20 MB/s even on a fast NAS, while a single 10GB video file on the same system transfers at 100+ MB/s.

Solutions: zip or tar large folders before transferring, use rsync instead of SMB for large backup operations (rsync is dramatically more efficient for mixed workloads), or use Nextcloud’s sync client which optimizes small-file transfers better than Windows file copy.