From: Stefan Kangas <stefankangas@gmail.com>
To: Christopher Howard <christopher@librehacker.com>, 74855@debbugs.gnu.org
Cc: Michael Albinus <michael.albinus@gmx.de>
Subject: bug#74855: 30.0.92; dired - slow copy across (wireless) LAN
Date: Wed, 18 Dec 2024 23:31:21 -0500 [thread overview]
Message-ID: <CADwFkmn_U6E7_9YW9w2AL5DsxcQdnjkDHTv+QideL72UdD3KDA@mail.gmail.com> (raw)
In-Reply-To: <87ikrna69c.fsf@librehacker.com>
Christopher Howard <christopher@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?
next prev parent reply other threads:[~2024-12-19 4:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-13 16:37 bug#74855: 30.0.92; dired - slow copy across (wireless) LAN Christopher Howard
2024-12-19 4:31 ` Stefan Kangas [this message]
2024-12-19 11:48 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CADwFkmn_U6E7_9YW9w2AL5DsxcQdnjkDHTv+QideL72UdD3KDA@mail.gmail.com \
--to=stefankangas@gmail.com \
--cc=74855@debbugs.gnu.org \
--cc=christopher@librehacker.com \
--cc=michael.albinus@gmx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).