GNU bug report logs - #74855
30.0.92; dired - slow copy across (wireless) LAN

Previous Next

Full log

Message #11 received at 74855 <at> debbugs.gnu.org (full text, mbox):

From: Michael Albinus <michael.albinus <at> gmx.de>
To: Stefan Kangas <stefankangas <at> gmail.com>
Cc: Christopher Howard <christopher <at> librehacker.com>, 74855 <at> debbugs.gnu.org
Subject: Re: bug#74855: 30.0.92; dired - slow copy across (wireless) LAN
Date: Thu, 19 Dec 2024 12:48:22 +0100

Stefan Kangas <stefankangas <at> gmail.com> writes:

> Christopher Howard <christopher <at> librehacker.com> writes:
>
>> Hello. Recently I was using dired to transfer 600 files, with about
>> 2GB data total, across our LAN (one wi-fi hop involved). The source
>> was a local directory, and the target was an SSH host on the LAN. I
>> marked the files I wanted with dired-mark-files-regexp, and then
>> used dired-do-copy to send them to
>> "/ssh:<snip>@<snip>:/home/<snip>/<snip>". This took a really long
>> time. Actually, the copy was still going after about 15 hours
>> (overnight) though I could see it had not frozen up, but was still
>> moving files.
>>
>> Using scp directly, from Gnome console, I am seeing transfer rates
>> of about 2.5 MB/s over the same path. So, I'm wondering why the
>> large disparity. Could somebody explain further how Emacs goes about
>> moving the file data and where the bottleneck would be. Is there
>> room for improvement in this functionality?
>
> Michael, any comments?

Tramp's "ssh" method is not suited for this use case. It encodes the
local file with base64, and decodes it when it has been arrived on the
remote side.

For this given use case, Tramp's "scp" method is better suited. See the
discussion in the manual, (info "(tramp) Connection types") and (info
"(tramp) Frequently Asked Questions") , the entry "How to speed up TRAMP".

Best regards, Michael.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.