From: Phil Sainty <psainty@orcon.net.nz>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 49264@debbugs.gnu.org, Ergus <spacibba@aol.com>
Subject: bug#49264: 28.0.50; project.el+tramp performance issue
Date: Thu, 01 Jul 2021 01:25:07 +1200 [thread overview]
Message-ID: <116428124d5c9911116bc992b360f2d7@webmail.orcon.net.nz> (raw)
In-Reply-To: <83sg0zmsf1.fsf@gnu.org>
On 2021-07-01 00:46, Eli Zaretskii wrote:
>> As a note here, when N files are in the same directory the normal
>> thing
>> is that all of them share the VCS. So calling a check function for all
>> of them is redundant and slow.
>
> AFAIR, that's not really true, and ISTR project.el aims to support the
> use cases with several different VC backends.
It's probably worth considering that while one *can* have multiple VC
backends active in a single directory, it's *extremely* common not to.
If there was a user option which effectively opted out of the multiple-
backend support in favour of performance-oriented assumptions and
caching, along with some mechanism for flushing the cache on demand
(advertised to the user as part of the user option documentation),
then users could then enable that option as a performance measure
provided that they were confident that the default functionality was
redundant for their use-cases (as I suspect it would be for many
people).
-Phil
next prev parent reply other threads:[~2021-06-30 13:25 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87fsx13aiz.fsf.ref@aol.com>
2021-06-28 22:11 ` bug#49264: 28.0.50; project.el+tramp performance issue Ergus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-06-29 12:05 ` Eli Zaretskii
2021-06-29 22:21 ` Ergus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-06-30 12:46 ` Eli Zaretskii
2021-06-30 13:25 ` Phil Sainty [this message]
2021-06-30 13:35 ` Eli Zaretskii
2021-06-30 15:10 ` Ergus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-06-29 13:00 ` Dmitry Gutov
2021-06-30 0:01 ` Ergus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-07-26 16:56 ` Ergus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-07-26 23:04 ` Dmitry Gutov
2021-08-09 0:59 ` Dmitry Gutov
2021-08-17 0:45 ` Ergus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-08-19 1:19 ` Dmitry Gutov
2021-08-19 3:08 ` Ergus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-08-21 2:23 ` Dmitry Gutov
2021-08-21 5:43 ` Ergus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-08-21 10:59 ` Dmitry Gutov
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=116428124d5c9911116bc992b360f2d7@webmail.orcon.net.nz \
--to=psainty@orcon.net.nz \
--cc=49264@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=spacibba@aol.com \
/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).