unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Albinus via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: Ergus <spacibba@aol.com>,
	73718@debbugs.gnu.org, Juri Linkov <juri@linkov.net>
Subject: bug#73718: 31.0.50; Severe performance issue with Tramp and project-mode-line-format
Date: Fri, 11 Oct 2024 13:45:49 +0200	[thread overview]
Message-ID: <87h69iuaky.fsf@gmx.de> (raw)
In-Reply-To: <744689a8-8631-4bcf-b040-00f62ec0eaba@yandex.ru> (Dmitry Gutov's message of "Fri, 11 Oct 2024 03:33:05 +0300")

Dmitry Gutov <dgutov@yandex.ru> writes:

Hi Dmitry,

>>> I wonder if we'll need to disable project-mode-line in remote files
>>> altogether, or if this is a problem that could be solved in Tramp
>>> (with extra caching?)
>> What do you think should be cached in Tramp?
>
> Not sure if more cache should be the answer here, but in the profile I
> see the hack-dir-local-variables call.
>
> So first, it should do nothing unless enable-remote-dir-locals is set
> to t (right?), so my first guess would be Ergus has customized that
> var. Maybe try turning it off, does that lose some features that you
> use?

Neither Tramp nor connection-local variables need this. Perhaps, it is a
good idea idea to bind enable-remote-dir-locals to nil in
project-mode-line-format.

> Second, I suppose Tramp could do some caching for the result of
> hack-dir-local--get-variables (just time-based), but I'm not sure how
> much it will help, on average. Only every 100th redisplay causing a
> stutter would still be a problem.

A redisplay shouldn't happen anymore, at least not triggered by
Tramp. I've added the NODISP arg to the respective sit-for call.

Best regards, Michael.





      reply	other threads:[~2024-10-11 11:45 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <874j5lzhdn.fsf.ref@aol.com>
2024-10-09 10:43 ` bug#73718: 31.0.50; Severe performance issue with Tramp and project-mode-line-format Ergus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-09 13:12   ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-10 11:12     ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-09 13:38   ` Dmitry Gutov
2024-10-09 13:45     ` Ship Mints
2024-10-09 14:01       ` Ship Mints
2024-10-09 16:10     ` Juri Linkov
2024-10-11  0:38       ` Dmitry Gutov
2024-10-11 14:35         ` Ship Mints
2024-10-13 13:31           ` Ship Mints
2024-10-10  9:57     ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-11  0:33       ` Dmitry Gutov
2024-10-11 11:45         ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors [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=87h69iuaky.fsf@gmx.de \
    --to=bug-gnu-emacs@gnu.org \
    --cc=73718@debbugs.gnu.org \
    --cc=dgutov@yandex.ru \
    --cc=juri@linkov.net \
    --cc=michael.albinus@gmx.de \
    --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).