From: Dmitry Gutov <dgutov@yandex.ru>
To: Ergus <spacibba@aol.com>, 49264@debbugs.gnu.org
Subject: bug#49264: 28.0.50; project.el+tramp performance issue
Date: Tue, 29 Jun 2021 16:00:02 +0300 [thread overview]
Message-ID: <72c1b336-ae02-36c0-db40-f608bafecdf3@yandex.ru> (raw)
In-Reply-To: <87fsx13aiz.fsf@aol.com>
Hi!
Thanks for the report, I'll follow up on this discussion some more
later, but some initial observations:
On 29.06.2021 01:11, Ergus via Bug reports for GNU Emacs, the Swiss army
knife of text editors wrote:
> As a workaround I removed all the uninteresting handlers from
> vc-handled-backends and I get better times now, but IMHO it is still
> very inefficient (almost a minute for project-switch-to-buffer is
> excessive). And make it practically unusable.
Could you evaluate (benchmark 1 '(project-current)) in one of your
buffers? That should give us an estimate how long it takes to find the
"current project" on your remote system.
If I'm right, project-switch-to-buffer should take 25 x (that time).
If you indeed only have 25 buffers (including hidden ones).
> In any case:
>
> Maybe (I think I mentioned this before) `project.el` needs a sort of
> cache to speedup some functions like `project-current` that are called
> very frequently inside the project.el code.
The difficulty here is probably with the large latency to the remote
system. And our current approach calls the "find current project" logic
for each open buffer.
Even if we add the "current project" cache, it will only take effect at
second and further invocations. Your first project-switch-to-buffer call
will still take 3-5 minutes, which is unacceptable.
Please get back to us with the requested measurements, and perhaps other
observations (any research initiative is welcome), but if finding the
current vc root for each buffer is unavoidably slow, we'll finally need
to switch to a "project-contains-buffer-p generic" approach, previously
discussed in e.g. "Speed up project-kill-buffers" thread on emacs-devel.
next prev parent reply other threads:[~2021-06-29 13:00 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
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 [this message]
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=72c1b336-ae02-36c0-db40-f608bafecdf3@yandex.ru \
--to=dgutov@yandex.ru \
--cc=49264@debbugs.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).