![]() Most SFTP clients (including WinSCP) overcome the problem by both requesting/sending a large chunk of the file in each single read/write request and by sending (queuing) multiple requests without waiting for a response to previous. If the client spends this time uselessly waiting, your transfer speed will be low. When transferring, the SFTP client (WinSCP) sends a read/write request to the SFTP server, waits for a response and repeats, until the end of the file.Įven if your connection is fast, if the server is far away (or slow), it takes a time for the response to arrive back. Network delay/latency affects particularly SFTP, as it is a packet oriented-protocol. It may also help, if you turn off compression, if you have turned it on before. ![]() Blowfish is usually a lot faster than AES. 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). Use the Windows Task manager to see, if one of the cores is utilized to its maximum during the transfer. 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. 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. When using SSH or TLS/SSL, file transfers in WinSCP are encrypted and encryption is CPU intensive.
0 Comments
Leave a Reply. |