From: Philippe Vaucher <philippe.vaucher@gmail.com>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: Michael Albinus <michael.albinus@gmx.de>,
Stefan Monnier <monnier@iro.umontreal.ca>,
Emacs developers <emacs-devel@gnu.org>
Subject: Re: emacs-27 b46c75b: xref-matches-in-files: Big Tramp speed-up
Date: Mon, 13 Jan 2020 10:50:48 +0100 [thread overview]
Message-ID: <CAGK7Mr46Vk8xw04NNRHCwoTcKt9h5_nbN0cW9mB2AVRve_t7ww@mail.gmail.com> (raw)
In-Reply-To: <fed14541-f4a9-8139-b688-03ffb62596ff@yandex.ru>
[-- Attachment #1: Type: text/plain, Size: 812 bytes --]
>
> On 08.01.2020 22:51, Stefan Monnier wrote:
> > Yes, I saw that, but it's still not clear to me which part of this costs
> > so much more than tramp-file-local-name itself, nor why.
>
> The whole of it, mostly. I've shown a simple patch which improved
> performance a lot, by Michael says it's unmaintainable (IIUC):
I'm not sure wether what I'll say is relevant to this discussion (please
forgive me if it is not), but I just wanted to mention that a significant
part of "debugging TRAMP problems" in projects like projectile is related
to TRAMP's speed.
I always assumed it was due to the fact that checking file attributes over
SSH is unavoidably slower than doing it locally, but if TRAMP can be
improved for things like `locate-dominating-file` over TRAMP it'd be a huge
help.
Kind regards,
Philippe
[-- Attachment #2: Type: text/html, Size: 1138 bytes --]
prev parent reply other threads:[~2020-01-13 9:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200107133628.1996.14412@vcs0.savannah.gnu.org>
[not found] ` <20200107133629.2E736211A5@vcs0.savannah.gnu.org>
[not found] ` <87y2uiiakq.fsf@gmx.de>
2020-01-08 13:52 ` emacs-27 b46c75b: xref-matches-in-files: Big Tramp speed-up Dmitry Gutov
2020-01-08 14:13 ` Michael Albinus
2020-01-08 14:56 ` Stefan Monnier
2020-01-08 15:13 ` Michael Albinus
2020-01-08 16:25 ` Stefan Monnier
2020-01-08 16:40 ` Michael Albinus
2020-01-08 18:56 ` Stefan Monnier
2020-01-08 20:10 ` Michael Albinus
2020-01-08 20:51 ` Stefan Monnier
2020-01-08 23:42 ` Dmitry Gutov
2020-01-13 9:50 ` Philippe Vaucher [this message]
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=CAGK7Mr46Vk8xw04NNRHCwoTcKt9h5_nbN0cW9mB2AVRve_t7ww@mail.gmail.com \
--to=philippe.vaucher@gmail.com \
--cc=dgutov@yandex.ru \
--cc=emacs-devel@gnu.org \
--cc=michael.albinus@gmx.de \
--cc=monnier@iro.umontreal.ca \
/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).