Windows to TrueNas Slow SMB Writes

So I am using SMB on my new TueNas Scale Dragon fish version of software.

my transfer speed from PC to Super Micro server is a terrible 25-29MB/s…
I can Transfer same video files to my Synology around 280MB/s -From Same PC
If i use NFS from my dell r720 the speeds are more respectable 220ish to the Super Micro server.

I cant find any help or why the Write speed is so slow on the SMB service.

For some reference the Super Micro has Dual E5-2620, 32Gb ram, Hard drives is x36 Dell EMC 8TB drives - From what i gather they are WD drives… 4 x RaidZ2 9 Wide, Have 2 Intel 1.92TB DC SSD in mirror for Write cache, triple mirror Meta Data Intel 1.92TB DC SSD… before i put the SSD drives in write speed’s were the same.
For the network the Super Micro is using Intel Dual SFP nic connected to 10Gbit fiber, other servers and PC’s connected only to 2.5Gbit nic’s. With 10Gbit uplinks.

Depending on the model from WD they could be SMR drives, which are known to are slow and cause other problems.
What do you mean by write cache? l2arc or slog? because l2arc is a read cache and slog is only useful with sync writes and won’t do anything when you’re using smb.

Hi, person familiar with the setup here.

He means Log

As it stands there are:

an R720 running Unraid
a Micro running TrueNAS scale
a Synology NAS
and his PC running windows

He can pull files from the Micro to PC at decent speeds (~200MB/s) on SMB
He can push files from R720 and Synology to Micro at decent speeds (~200MB/s) on NFS
but any attempt to push from PC to Micro on SMB results in <30MB/s speeds

I don’t understand what is causing the issue when pushing files from Windows to TrueNAS when every other device, regardless of network location, can push files at a decent rate. Can SMB on TrueNAS just not accept files that fast?

Screenshot 2024-08-23 034240

As far as i was able to google the Drives seem to be CMR not SMR, which is good.
I would start with an iperf from windows pc to truenas to rule out any network problems, because it sounds like maybe the 2.5gb nics aren’t running at full speed.
And again, depending on the usecase the mirrored slogs are completely useless…

So I presume you mean SLOG device? If so this may only be helpful for sync writes which SMB is async (so not helpful at all). I don’t suppose you have told your SMB dataset to sync writes have you? Perhaps you could post a screenshot of your dataset settings?

nic is fine i can write at 280MB/s to the synology and pull at 280MB/s

Used my kids computer with diffrent network setup and results are same.

Best question yet, the sync was set to inherit (STANDARD), so changed to always, Standard, and speed went from 20MB/s to 30MB/s.
So to Always and getting 40MB/s
Still so after much reading their is talk about single thread and such… i really dont think a dual Intel Xeon E5-2620 should be the bottle neck?? It turbos to 2.5Ghz

Did some comparing, i used the cpubenchmark.net their results the Xeon is 8% slower on a single core task, so that could not cause a drop from the 280MB/s the synology can write at.

If it helps any the synology is a DS1821+ upgraded with 2x Samsung 1Tb NVme and 32Gb ram with 2.5Gbit nic, Rocking 8 Seagate exos x20 20Tb drives.

Still worthwhile running an iperf3 test from windows to/from truenas.

There is an iperf3 client built into truenas.

Standard should be fine but if you’re going to do anything turn it off NOT always that should make things slower.

Can you run zfs get all pool/dataset from the CLI and output the results.

Agreed. A single thread anything should saturate 1Gb so ignore that.

Have you done any local benchmarks with FIO?


That is to the True Nas from PC


This is data from True nas to PC


This is PC to UnRaid

image
This is Dell “Unraid” to True Nas

So, you have a networking issue between the pc and truenas.

Not an SMB or storage configuration issue.

1 Like

what is strange is that PC->TRUENAS is slower than TRUENAS->PC
and if i’m not mistaken we would get the same results from a different windows pc because we were seeing the same data transfer speeds when moving files

topologies:

PC-----SODOLA Switch-----MOKER LINK-----TRUENAS

PC 2-----SODOLA Switch 2-----MOKER LINK-----TRUENAS

Unraid----SODOLA Switch 3-----Bit Engine Switch-----MOKER LINK----TRUENAS

the only common denominator is Windows->TrueNAS speeds being slow

May be a tcp configuration issue. Ie window size, congestion control etc

I suspect a Windows issue or possibly specifically an issue with iperf3 for Windows. (what iperf3 version are you running in Windows?) Nevermind, I see the binary is in a folder with the version in the name, 3.17.1.

It would be useful to check what happens if you connect something not Windows-based with the network cable PC is currently using. Then run a iperf3 test with everything else unchanged.

I did show a result from the “MY” pc transmitting to another server and speeds are great. So i struggle to believe its that hard ware.
So next Test was kids computer to the Truenas
Screenshot_2024-08-23_120230
So to clarify, the only common point in network equipment is the mokerlink and SFP / Fibre. to dual SFP 10Gbit intel nic. and yet it can receive fine from other servers,

The only real pattern i see is a windows PC slow in to true nas, and any thing linux based work fine. With windows PC to any other server is fine… Also i reinstalled the Truenas OS last night and was no better.

note: so darn frustrated,

The fact that the same PC iperf3 tests he posted show vastly different speeds to the supermicro running truenas and the r720 running unraid tells me that the iperf3 windows binary is fine.
When I get the opportunity in the next few days I will try to grab my linux usb and go visit him.
I’m curious what will happen if we boot his PC into linux and run iperf3 again with the same hardware and only a diff OS.
But the fact that he has similar results testing from another Windows PC to TrueNAS really makes it look like some kind of interoperability issue between the two OSes, but then everyone would have the issue so my confusion persists.
I’ll post in a few days with the results of the next test and hopefully smarter minds than I can point me in the next direction.