Skip to content
This repository has been archived by the owner on Apr 19, 2024. It is now read-only.

Slow download network speed over plink #274

Open
vovcacik opened this issue Aug 12, 2017 · 1 comment
Open

Slow download network speed over plink #274

vovcacik opened this issue Aug 12, 2017 · 1 comment
Labels

Comments

@vovcacik
Copy link
Contributor

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
Client side setup
set path=C:\Program Files\OpenSSH;C:\putty;%PATH%
  • and the benchmark:
# Win32-OpenSSH performance

scp [email protected]:binfile binfile
echo 12.66s

ssh [email protected] cat binfile > binfile
echo 12.74s

unison nano
echo 12.41s



# PuTTY, PuTTYTray performance

pscp -scp [email protected]:binfile binfile
echo 12.91s

pscp -sftp [email protected]:binfile binfile
echo 12.85s

plink -V
plink: Release 0.66
plink [email protected] cat binfile > binfile
echo 74.00s

plink -V
plink: PuTTYTray p0.66-t028
plink [email protected] cat binfile > binfile
echo 73.18s

plink -V
plink: PuTTYTray p0.67-t029
plink [email protected] cat binfile > binfile
echo 75.60s

unison nano
echo 107.64s

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.

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.

@T-O-W
Copy link

T-O-W commented Oct 30, 2017

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.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

3 participants