I have improved WinSCP by increasing its receive buffer. What should improve download speed, without a need to tweek Windows registry. Anyone willing to test?
Before posting, please read how to report bug or request support effectively.
Bug reports without an attached log file are usually useless.
Some clients support this capability. I'm not sure that is is part of the FTP protocol itself, but a workaround where the client perhaps opens several control connections - not sure.
Here's a client that supports it - https://help.globalscape.com/help/cuteftp9/Making_multiple_concurrent_connections.htm
It seems that WinSCP, when configured for FTP over TLS (FTPS), opens a separate TCP connection for each file transfer. For copying folders with many files and sub-directories, this is extremely inefficient. Each new TCP connection needs to get the certificate before the transfer. Shouldn't there be a way of re-using existing open connections? And re-using multiple concurrent connections at that?
Thanks for sharing this!
I've also tried every encryption algorithm, multiple machines, SFTP vs SCP, SSH1 vs SSH2, etc. Everything I do on multiple machines seems to be capped at around 100KBps upload speed. One machine is a Core 2 Duo at 2.0GHz with a 7200rpm disk and while WinSCP is uploading, the CPU idles at around 10% or so, no where near it's processing limit. This happens on both Windows Vista SP1 and Windows XP SP2. We've tested our routers and firewalls by using a slower Linux machine that easily uploads at our full upload bandwidth (7.5Mbps).
Have you tried psftp/pscp?
So I know scp eats CPU power but why not under Linux?