akami Posted February 27, 2023 Share Posted February 27, 2023 With unraid smb all default settings: sftp is 7.9x faster than smb sftp also get lower cpu usage nvme-cow: TotalRead = 62 MiB TotalWrite = 62 MiB TotalFiles = 2,926 (335) TotalTime = 01:19 TransRate = 0.81 MB/s FileRate = 36.6 files/s nvme-nocow: TotalRead = 62 MiB TotalWrite = 62 MiB TotalFiles = 2,926 (335) TotalTime = 01:37 TransRate = 0.67 MB/s FileRate = 30.1 files/s hdd*1(xfs) TotalRead = 62 MiB TotalWrite = 62 MiB TotalFiles = 2,926 (335) TotalTime = 01:34 TransRate = 0.69 MB/s FileRate = 30.9 files/s smb win11->unraid(nvme raid1 cache pool) nvme-cow: 01:19 nvme-nocow: 01:37 hdd*1(xfs): 01:34 win11(pc)->win10(pc-vm): 39s sftp win11->unraid(nvme raid1 cache pool) cow=nocow=hdd*1(xfs)=10s Quote Link to comment
akami Posted February 28, 2023 Author Share Posted February 28, 2023 (edited) via docker: drakkan/sftpgo: ftp 64s sftp 50s crazymax/pure-ftpd: 14s Edited February 28, 2023 by akami Quote Link to comment
Solution JorgeB Posted February 28, 2023 Solution Share Posted February 28, 2023 Try using the disk path/share, user share always add some overhead. Quote Link to comment
akami Posted February 28, 2023 Author Share Posted February 28, 2023 (edited) On 2/28/2023 at 4:43 PM, JorgeB said: Try using the disk path/share, user share always add some overhead. When Docker mounts a path to /mnt/cache/xxx, there is no shfs process usage. New folder with 70k files via docker sftpgo-ftp rclone--transfers=16 11m14.9s sftpgo-sftp rclone--transfers=16 11m7.4s syncthing 10m52s via unraid build-in sftp host-sftp 2m6s Transferring many files via docker is still slow, docker's wirte operation is direct to disk. However, via native sftp, data is cached in ram and written to disk. Edited March 8, 2023 by akami correct data Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.