Differences

This shows you the differences between the selected revisions of the page.

2018-08-30 2018-08-30
limit acronym recognition (martin) Optimize connection buffer size, based on t=25705 (martin)
Line 4: Line 4:
In case the speed is throttled by %%CPU%%, it may help if you choose different encryption algorithm on //[[ui_login_ssh#encryption_options|SSH page]]// of Advanced Size Settings dialog (supposing you are using SSH-based [[protocols|file transfer protocol]], such as SFTP or SCP). When using %%SSH%%, file transfers in WinSCP are encrypted and encryption is %%CPU%% intensive. Either your local workstation or your server might not be able to encrypt file transfer stream at the same speed, your connection is able to transfer it. //Blowfish// is usually a lot faster than //AES//. It may also help if you turn off [[ui_login_ssh#protocol_options|compression]], if you have turned it on before. In case the speed is throttled by %%CPU%%, it may help if you choose different encryption algorithm on //[[ui_login_ssh#encryption_options|SSH page]]// of Advanced Size Settings dialog (supposing you are using SSH-based [[protocols|file transfer protocol]], such as SFTP or SCP). When using %%SSH%%, file transfers in WinSCP are encrypted and encryption is %%CPU%% intensive. Either your local workstation or your server might not be able to encrypt file transfer stream at the same speed, your connection is able to transfer it. //Blowfish// is usually a lot faster than //AES//. It may also help if you turn off [[ui_login_ssh#protocol_options|compression]], if you have turned it on before.
-In case the speed is throttled by connection latency, it may help if you use [[scp|SCP protocol]] instead of [[sftp|SFTP]]. %%SCP%% is less affected by latency. In this case, it may help if you turn on [[ui_login_ssh#protocol_options|compression]].+In case the speed is throttled by connection latency, it may help if you use [[scp|SCP protocol]] instead of [[sftp|SFTP]]. %%SCP%% is less affected by latency. In this case, it may help if you turn on [[ui_login_ssh#protocol_options|compression]]. Toggling //[[ui_login_connection|Optimize connection buffer size]]//, in either way, can help too.
Also there's a lots to improve in performance of WinSCP itself [[bug>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. Also there's a lots to improve in performance of WinSCP itself [[bug>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.

Last modified: by martin