Bug 339830

Summary: Slow file transfer (fish, sshfs)
Product: [Frameworks and Libraries] kio-extras Reporter: Zsolt Z. <zakalzs>
Component: FISHAssignee: Jörg Walter <trouble>
Status: REPORTED ---    
Severity: normal CC: aspotashev, empire, gennady.uraltsev, kishore96, nate, postix, suse, toni.asensi, v
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
See Also: https://bugs.kde.org/show_bug.cgi?id=342056
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Zsolt Z. 2014-10-09 19:35:56 UTC 
Copying from local machine to a remote host with sshfs (dolphin, fish://) is very slow.

For example copying an 50MB test file from my computer to  my VPS:
With scp:    ~5 MB/sec 
With dolphin (KIO, fish://):    ~500 KB/sec

Another server:
With scp:    ~2 MB/sec
With dolphin (KIO, fish://):    ~80-90 KB/sec










Reproducible: Always
Comment 1 suse 2015-04-28 19:36:49 UTC 
another performance example:
host: openSUSE 13.2
client: virtualbox with OpenSUSE tumbleweed and Plama 5.3

with scp: ~ 90-100MB/s which nearly reaches the 1GB/s link speed.
with dolpin's  sftp:// only 10MB/s
Comment 2 V 2018-05-23 15:19:10 UTC 
I'm experiencing the same problem in Dolphin 18.04.0 in openSuSE 42.
fish:// protocol in Dolphin gives about 30 KB/s, while simple scp in terminal gives 500 KB/s.
Comment 3 Alexander Potashev 2018-11-18 20:03:11 UTC 
It is even slower when copying from one ssh remote to another. I've got these results testing copying KIO fish:
 1. server A -> local: 1100 KB/s
 2. local -> server B: 180 KB/s
 3. server A -> server B: 24 KB/s
Comment 4 Alexander Potashev 2018-11-18 20:03:43 UTC 
(In reply to Alexander Potashev from comment #3)
> It is even slower when copying from one ssh remote to another. I've got
> these results testing copying KIO fish:
>  1. server A -> local: 1100 KB/s
>  2. local -> server B: 180 KB/s
>  3. server A -> server B: 24 KB/s

(I was copying one large file in all of these tests.)
Comment 5 Alexander Potashev 2018-11-18 20:04:19 UTC 
May be related to bug #342056