unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Albinus <michael.albinus@gmx.de>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org, Dmitry Gutov <dgutov@yandex.ru>
Subject: Re: emacs-27 b46c75b: xref-matches-in-files: Big Tramp speed-up
Date: Wed, 08 Jan 2020 21:10:04 +0100	[thread overview]
Message-ID: <877e21iuar.fsf@gmx.de> (raw)
In-Reply-To: <jwv4kx57ugl.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Wed, 08 Jan 2020 13:56:03 -0500")

Stefan Monnier <monnier@iro.umontreal.ca> writes:

> But in the current case, we just replace N calls to `file-local-name` with
> N calls to `tramp-file-local-name` and it's supposedly already much
> faster, even though `tramp-file-local-name` doesn't get to share work
> between all those calls, AFAIK.  It's *this* speed difference which I'd
> like to understand.

I said it already several times: it is tramp-file-name-handler, invoked
for every single file, which makes the major difference.

And I don't know how to change its work significantly.

>> That's why I have proposed to find a way to apply an operation to a
>> fileset instead of a single file only.
>
> Yes, the idea makes sense.  Basically add a magic-file-op
> (file-list-apply FUNCTION DIR FILES &rest ARGS) where FILES are relative
> to DIR?

Something like this, yes. However, in the case Dmitry is interested in,
FILES would be remote file names instead of relative file names. He
wanted to know the local file name part of the FILES.

I will see how it could look like. Later this week.

>         Stefan

Best regards, Michael.



  reply	other threads:[~2020-01-08 20:10 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 [this message]
2020-01-08 20:51                     ` Stefan Monnier
2020-01-08 23:42                       ` Dmitry Gutov
2020-01-13  9:50                         ` Philippe Vaucher

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=877e21iuar.fsf@gmx.de \
    --to=michael.albinus@gmx.de \
    --cc=dgutov@yandex.ru \
    --cc=emacs-devel@gnu.org \
    --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).