Hide Forgot
Description of problem: When copying a large file over FUSE sshfs, or using sftp or scp, I see transfer rates of around 30 MB/s. When using gvfs-fuse when copying via a browsed SSH share using Nautilus, transfer rates typically drop to around 10 MB/s. Using cp on the remote file (i.e., the ~/.gvfs path obtained by dragging and dropping to the terminal) is only marginally faster (around 14 MB/s). Version-Release number of selected component (if applicable): nautilus-3.0.2-1.fc15.x86_64 gvfs-1.8.2-1.fc15.x86_64 gvfs-fuse-1.8.2-1.fc15.x86_64 openssh-5.6p1-34.fc15.1.x86_64 fuse-sshfs-2.3-1.fc15.x86_64
Present in F16. gvfs-1.10.1-2.fc16.x86_64 gvfs-fuse-1.10.1-2.fc16.x86_64
Present in F17. gvfs-1.12.2-1.fc17.x86_64 gvfs-fuse-1.12.2-1.fc17.x86_64
gvfs-fuse is more or less considered as a fallback with no performance goals. What is the speed you get in Nautilus, using regular GIO path?
(In reply to comment #3) > gvfs-fuse is more or less considered as a fallback with no performance goals. > What is the speed you get in Nautilus, using regular GIO path? I think I may have got the identification/nomenclature wrong. Sorry about that. Either way, I'm referring to file transfers in Nautilus over SFTP, where I've connected to the hosts via "Browse Network". I take it this is the "regular GIO path" -- run by gvfsd-sftp? Anyway: speed measurements. The kit: - server: SATA 5400 rpm HDD, Core2Duo T8100 (2.1 GHz), Realtek RTL8168b/8111b NIC (r8169) - client: SATA 5400 rpm HDD, i7-2760, Atheros AR8151 NIC (atl1c) - gigabit switch, cat 5e cables The data: F16 x86-64 live ISO image. Being transferred from server to client. Unscientific results: Via Nautilus (as above), the progress bar reports transfer speeds levelling off at around 13-14 MB/s. Via ordinary sftp, I get 37-38 MB/s. In this case, I note a much higher CPU usage in the server (near 100%).
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '17'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 17's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.