This is an old revision of the document!

File transfer speed is very low. WinSCP does not utilize all available bandwidth. How do I improve the transfer speed?

The transfer speed can be throttled by two factors (apart from bandwidth). CPU (computation power of machines on both sides) and connection latency (how long does it take for unit of data to transfer between the two machines).

Advertisement

CPU

When using SSH or TLS/SSL, file transfers in WinSCP are encrypted and encryption is CPU intensive. Either your local machine or your server might not be able to encrypt file transfer stream at the same speed, your connection is able to transfer it.

WinSCP as well as most (if not all) SFTP servers cannot distribute the encryption/decryption among CPU cores, so it’s actually a capacity of a single CPU core that limits the transfer speed.

Use the Windows Task manager to see, if one of the cores is utilized to its maximum during the transfer.

In case the speed is throttled by CPU, it may help if you choose different encryption algorithm on SSH page of Advanced Site Settings dialog (supposing you are using SSH-based file transfer protocol, such as SFTP or SCP). Blowfish is usually a lot faster than AES. It may also help, if you turn off compression, if you have turned it on before.

porn

Relation to PuTTY PSCP/PSFTP

Also there’s a lots to improve in performance of WinSCP itself 164. So it may get better in future versions.

Also note that as SSH code of WinSCP is based on PuTTY, file transfers with SSH-based protocols can hardly be faster than PuTTY (PSCP/PSFTP) is. Hence there is no point asking for speed improvements, if you get the same rate with PuTTY.

Logging

If WinSCP started being slow suddenly, check if you did not enable logging on “Debug” level inadvertently.

Advertisement

Last modified: by 95.85.128.26