You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 19, 2024. It is now read-only.
Hi,
I've noticed that plink download speed is considerably lower than the speed of other implementations. It only affects plink and only the download speeds; upload is as fast as others. I tried vanilla plink and PuTTYTray plink.
Server side setup
server is Debian running on Amazon's EC2
we just need some test file; in this case binfile of size 100 MiB in home dir
cd
dd if=/dev/zero of=binfile bs=$((2**20)) count=100
ls -la binfile
-rw-r--r-- 1 admin admin 104857600 Aug 12 11:10 binfile
You can see that plink is about 5x slower. I have included unison in the benchmark, as thats the real world use case here, but even the cat binfile over plink demonstrate the problem well.
I know this may not be the best place to ask this, but I wanted to bring this to your attention, because you may have better insight what could be wrong, or you may have noticed some build flags that could help to fix this.
The text was updated successfully, but these errors were encountered:
This might not be the same issue, but I observed that all tools based on PuTTYs file transfer implementation (WinSCP, FileZilla, PuTTY tools) have a considerably bad network performance. In a gigabit network, I can transfer files with only about 15 MB/s. First, I thought this was an issue with ciphers, but other tools (Bitvise SSH, Windows 10's Linux subsystem, a native Linux, ...) do a much better job (around 75 MB/s in my case) using the same ciphers.
I don't know what is wrong there, but it seems that PuTTY developers did a very bad job for file transfers. Still, I perfer PuTTY over Bitvise SSH for daily work, because it is more convenient. For big file transfers, I use Bitvise SSH.
Hi,
I've noticed that
plink
download speed is considerably lower than the speed of other implementations. It only affectsplink
and only the download speeds; upload is as fast as others. I tried vanillaplink
and PuTTYTrayplink
.Server side setup
binfile
of size 100 MiB in home dirClient side setup
ftp://ftp.chiark.greenend.org.uk/users/sgtatham/putty-0.66/
)rsync
)You can see that
plink
is about 5x slower. I have includedunison
in the benchmark, as thats the real world use case here, but even thecat binfile
overplink
demonstrate the problem well.There is also very nice question on serverfault.com Copying over SSH via Putty tools is slower than via WinSCP.
I know this may not be the best place to ask this, but I wanted to bring this to your attention, because you may have better insight what could be wrong, or you may have noticed some build flags that could help to fix this.
The text was updated successfully, but these errors were encountered: