From: Eli Zaretskii <eliz@gnu.org>
To: "Simen Heggestøyl" <simenheg@runbox.com>
Cc: 51006@debbugs.gnu.org
Subject: bug#51006: 28.0.60; Slowness while navigating in inferior-python-mode
Date: Mon, 04 Oct 2021 16:24:33 +0300 [thread overview]
Message-ID: <835yuc7wj2.fsf@gnu.org> (raw)
In-Reply-To: <87fsthympr.fsf@runbox.com> (message from Simen Heggestøyl on Mon, 04 Oct 2021 14:54:24 +0200)
> From: Simen Heggestøyl <simenheg@runbox.com>
> Date: Mon, 04 Oct 2021 14:54:24 +0200
>
> Here's the report from a quick profiling I did in Emacs 28:
>
> 13447 94% - python-shell-font-lock-post-command-hook
> 13444 94% - font-lock-ensure
> 13444 94% - #<compiled -0x19f3968dc99b6307>
> 13444 94% - font-lock-fontify-region
> 13444 94% - font-lock-default-fontify-region
> 13420 94% - font-lock-fontify-syntactically-region
> 13420 94% - python-font-lock-syntactic-face-function
> 13412 94% - python-info-docstring-p
> 13396 94% + python-nav-beginning-of-statement
> 4 0% + python-info-assignment-statement-p
> 8 0% + font-lock-fontify-keywords-region
> 3 0% + font-lock-mode
> 529 3% + ...
> 183 1% + command-execute
Please repeat the profiling experiment, but after loading python.el
(NOT python.elc). This should produce a more detailed profile that
would pinpoint the culprit more accurately. Based on skimming the
source code, my first suspect is syntax-ppss, but that could be a bad
guess.
Thanks.
next prev parent reply other threads:[~2021-10-04 13:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-04 12:54 bug#51006: 28.0.60; Slowness while navigating in inferior-python-mode Simen Heggestøyl
2021-10-04 13:24 ` Eli Zaretskii [this message]
2021-10-04 19:21 ` Simen Heggestøyl
[not found] ` <87mtno8ujv.fsf@simenheg@gmail.com>
2021-10-04 19:52 ` Eli Zaretskii
2022-07-22 9:41 ` Simen Heggestøyl
2022-07-22 11:22 ` Eli Zaretskii
2022-07-22 20:06 ` Lars Ingebrigtsen
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=835yuc7wj2.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=51006@debbugs.gnu.org \
--cc=simenheg@runbox.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.