From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: emacs-pretest-bug@gnu.org,
Stephen Berman <Stephen.Berman@gmx.net>,
emacs-devel@gnu.org
Subject: Re: 22.1.50; insert-file-contents is slow under tramp
Date: Fri, 24 Aug 2007 10:32:19 -0400 [thread overview]
Message-ID: <jwvwsvlt3ch.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87bqcxzeat.fsf@gmx.de> (Michael Albinus's message of "Fri\, 24 Aug 2007 07\:34\:18 +0200")
>> So I hope there's a better way.
> Yes. I've installed a patch in the trunk, which makes a fast track for
> "remote" files being on localhost.
How does that work? I mean when accessing files on the localhost with
Tramp, the most likely situation I can think of is the `su' method so how
what does your "fast track" do to transfer the file faster? Does it copy it
to /tmp at the "remote" end, then make it world-readable, then copy it on
the "local" end, then remove it at the remote end?
> For real remote hosts, I recommend to use scp when accessing huge files.
Reminds me: where is the bottleneck in the inline method? I mean
fundamentally doing a base64 encoding/decoding shouldn't cost that much
(negligible CPU-wise and a mere 33% in network transfer). Maybe we could
attack this part to improve performance?
Stefan
next prev parent reply other threads:[~2007-08-24 14:32 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-23 12:33 22.1.50; insert-file-contents is slow under tramp Stephen Berman
2007-08-23 14:25 ` martin rudalics
2007-08-23 15:02 ` Stephen Berman
2007-08-23 17:49 ` martin rudalics
2007-08-23 18:59 ` Stefan Monnier
2007-08-23 20:25 ` martin rudalics
2007-08-23 20:39 ` Stephen Berman
2007-08-23 21:01 ` martin rudalics
[not found] ` <46CDF5B7.2030201@g\x04mx.at>
2007-08-23 21:40 ` Stephen Berman
2007-08-24 5:34 ` Michael Albinus
2007-08-24 7:18 ` Stephen Berman
2007-08-24 14:32 ` Stefan Monnier [this message]
2007-08-26 10:36 ` Michael Albinus
2007-08-26 19:01 ` David Kastrup
2007-08-26 19:24 ` Michael Albinus
2007-08-27 4:16 ` Stefan Monnier
2007-08-27 11:41 ` Michael Albinus
2007-08-27 13:58 ` Stefan Monnier
2007-08-27 14:09 ` Thien-Thi Nguyen
2007-08-27 14:14 ` David Kastrup
2007-08-27 14:53 ` Michael Albinus
2007-08-27 20:11 ` Stefan Monnier
2007-08-27 20:37 ` Michael Albinus
2007-08-27 10:52 ` Michael Albinus
2007-08-27 11:33 ` David Kastrup
2007-08-27 18:18 ` Richard Stallman
2007-08-27 18:51 ` David Kastrup
2007-08-24 9:28 ` Eli Zaretskii
2007-08-24 9:35 ` Stephen Berman
2007-08-24 16:10 ` Richard Stallman
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=jwvwsvlt3ch.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=Stephen.Berman@gmx.net \
--cc=emacs-devel@gnu.org \
--cc=emacs-pretest-bug@gnu.org \
--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).