GNU bug report logs -
#49264
28.0.50; project.el+tramp performance issue
Previous Next
Reported by: Ergus <spacibba <at> aol.com>
Date: Mon, 28 Jun 2021 22:12:02 UTC
Severity: normal
Found in version 28.0.50
Done: Dmitry Gutov <dgutov <at> yandex.ru>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
[Message part 1 (text/plain, inline)]
Hi Ergus,
On 17.08.2021 03:45, Ergus wrote:
> I made a manual fast profiling and I see that most of the time in
> project-buffers actually goes to tramp-sh-file-name-handler.
>
> 207 42% - project-buffers
> 207 42% - apply
> 207 42% - #<compiled -0x1f5d919efefc0a09>
> 200 40% - file-in-directory-p
> 200 40% - tramp-file-name-handler
> 197 40% - apply
> 197 40% - tramp-sh-file-name-handler
> 197 40% - tramp-handle-file-in-directory-p
> 183 37% - tramp-run-real-handler
> 183 37% - file-in-directory-p
> 124 25% - file-equal-p
> 124 25% - tramp-file-name-handler
> 121 24% - apply
> 121 24% - tramp-sh-file-name-handler
> 121 24% - tramp-handle-file-equal-p
> 85 17% - tramp-run-real-handler
> 85 17% - file-equal-p
> 52 10% - file-truename
> 52 10% - tramp-file-name-handler
> 41 8% - apply
> 41 8% - tramp-sh-file-name-handler
> 41 8% -
> tramp-sh-handle-file-truename
> 28 5% + file-remote-p
> 10 2% + file-local-name
> 3 0% + file-name-as-directory
>
> It goes specifically to file-in-directory-p as you said. So maybe the
> improvement there may be also desirable if the difference after the
> optimization can reduce the time for file-in-directory-p (or the caller)
> at least to the half.
Thanks for testing.
Try the attached new version please. It should eliminate that particular
bottleneck.
[project-buffers.diff (text/x-patch, attachment)]
This bug report was last modified 3 years and 273 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.