Network speed limited to 300Mbps on gigabit connections
Network speed limited to 300Mbps on gigabit connections
The SSD serves as the servers' boot drive. You initially assumed the SSD was your Windows client, but for a NAS or Home Server it's better to avoid keeping data on the OS drive. If the drive fails, recovery is usually possible by importing it into a fresh OS installation; however, storing data directly on the OS disk means losing everything. Most valuable data isn't large enough to justify worrying about SSH performance. Still, proceeding with that assumption. What speeds did you achieve using SMB over Wi-Fi? If they're higher, I believe the SSH speeds you observe are realistic.
I understand I shouldn't store data there. I'm just taking a test file from the server's SSD to my laptop for performance checks. The HDD on the server is slow, limiting reads to around 27 MB/s. Using SMB over HDD gave me about 24 MB/s, while SSH via SSD reached up to 37 MB/s.
For measuring peak network performance between laptop and server, iperf provides a more accurate assessment. Results from iperf help rule out issues related to client storage or settings. It seems SSH delivers faster speeds, which is unusual—this might indicate a different underlying problem.
You're looking for a straightforward guide on setting up iperf for testing. Start with a simple step-by-step tutorial that explains the configuration process clearly.
Use simple instructions to begin a server with iperf3. After launching it, access the client and execute the provided command. On Windows, ensure the command prompt is in the correct folder for iperf3.exe.
It's interesting that a single HDD struggles to reach maximum Gigabit speeds. Most drives should handle 100MB/s for a continuous file, while NAS models can achieve up to 220MB/s. Comparing this to 2x2 MIMO 5GHz at 160Mhz on a nanoHD, which caps at 70MB/s, the difference is notable. Even with an 80Mhz channel on my phone, it manages similarly.