[kio] [Bug 291835] KIO very slow when copying from network through smb

Mauro Molinari mauromol at tiscali.it
Wed Apr 23 08:47:20 BST 2014


https://bugs.kde.org/show_bug.cgi?id=291835

Mauro Molinari <mauromol at tiscali.it> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |mauromol at tiscali.it

--- Comment #34 from Mauro Molinari <mauromol at tiscali.it> ---
I also noticed that file transfers through Dolphin using smb:/ and nfs:/
protocols are sensibly slower than doing the same file transfers from the same
shared folders mounted on the local file system. This is in contrast with the
performance I get if I use the ftp:/ protocol to access the same server, which
is very fast.
These are the transfer speeds I get on my 802.11g WLAN:
- reading from server with ftp:/ protocol in Dolphin: around 3,9 MB/s
- reading from server with smb:/ protocol in Dolphin: around 2,2 MB/s
- reading from server with nfs:/ protocol in Dolpin: around 1,9 MB/s
- reading from server using a SMB mount point: around 3,5 MB/s
- reading from server using a NFS mount point: around 3,9 MB/s
- reading from server using a curlftpfs mount point: around 500 kB/s (there
must be some severe problem with curlftpfs, but it's not important here)

Conclusion: said that 3,9 MB/s should be the maximum speed I can achieve using
my WLAN, ftp transfer with ftp:/ protocol in Dolphin is highly efficient, while
the same is not true for smb:/ and nfs:/ protocols (the latter is the worst
one!! And this was a surprise for me). 
This is a pity, because accessing shared resources in Dolphin without having to
mount them would be very handy, especially for the novice user and when
combined with resource bookmarking.

This evening I will make some tests using the wired Gigabit connection instead
of WLAN. I'm expecting even higher differences.

Using Linux Mint 16 KDE.

-- 
You are receiving this mail because:
You are the assignee for the bug.



More information about the Unassigned-bugs mailing list