Removed parity - still slow writing speed

[mgutt]

I started multiple wget processes (fetches files through FTP from source NAS). Each process writes files to different disks.

 

The Unraid server has 10G:

 

The source, too:

 

The load on the Unraid server looks good:

 

And on the source, too:

 

Finally I started a fourth wget process that targets disk 4. This wast the first time the transfer exceeded 1G:

 

Any idea why it could be so slow? I thought without parity it reaches the maximum write speed of the disk (up to 260 MB/s)?!

Edited April 21, 2020 by mgutt

[testdasi]

What does it say on the Main page?

[JorgeB]

Could also be transfer protocol (ftp) related, especially is it's a secure connection, ssh overhead is high, try netcat (nc), if it's a secure LAN.

 

 

[mgutt]

It's unsecure FTP. Should be fast.

25 minutes ago, testdasi said:

What does it say on the Main page?

 

P.S. it transfers mainly huge files (~25GB per file). 

Edited April 21, 2020 by mgutt

[JorgeB]

Very high CPU/system load for those transfers, try with a different protocol, your just SMB.

[JorgeB]

Also you can see real-time read/write speeds on the GUI, toggle is on the right upper corner:

 

 

[mgutt]

3 hours ago, johnnie.black said:

Also you can see real-time read/write speeds on the GUI, toggle is on the right upper corner

Nice to know.

 

It jumps like crazy between 0 and 80 MB/s per Disk. Looks like wget is working in chunks. 

Edited April 21, 2020 by mgutt

[mgutt]

Yes it was caused by wget. I tried the following smbclient command (source) and it hits the max write speed of the disk:

smbclient //10.1.2.3/video <smb_password> -U <smb_user> -c 'prompt ON; recurse ON; cd \Filme\KL\; lcd /mnt/user/Movies/KL/;mget *'

I started two processes and its really fast now:

 

Funnily the load is not really different:

 

Sadly the source NAS seems to hit its limit now:

 

At least, I think that, because I was not able to raise the network traffic by starting three parallel smbclient processes, so I think the "volume utilization" is the bottleneck, now. I never really found out what Synology meant with that.

 

P.S. I hope someone can answer this question because I did not found out how to skip existing / older files with the smbclient command.

 

Edited April 21, 2020 by mgutt