From: Eli Zaretskii <eliz@gnu.org>
To: Andrea Corallo <acorallo@gnu.org>
Cc: 65250@debbugs.gnu.org
Subject: bug#65250: 30.0.50; "C-h f" is much slower on the master branch
Date: Sat, 12 Aug 2023 20:23:39 +0300 [thread overview]
Message-ID: <83350odvj8.fsf@gnu.org> (raw)
In-Reply-To: <yp1fs4oci6g.fsf@fencepost.gnu.org> (message from Andrea Corallo on Sat, 12 Aug 2023 12:57:27 -0400)
> From: Andrea Corallo <acorallo@gnu.org>
> Cc: 65250@debbugs.gnu.org
> Date: Sat, 12 Aug 2023 12:57:27 -0400
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > To reproduce:
> >
> > emacs -Q
> > C-h f dictionary-search RET
> >
> > (almost any other function will do, I think).
> >
> > This takes a whopping 6.6 sec of CPU on master, vs 2.4 sec on the
> > emacs-29 branch. These are both unoptimized builds, but even so,
> > 6.6 seconds of CPU time for looking up a doc string of a function
> > is too much, I think.
> >
> > The patch below fixes the problem in a build without
> > native-compilation, but won't help in a build with native-compilation.
> > I wonder why comp-function-type-spec is so expensive?
>
> Hi Eli,
>
> can't look at this now, will do on Monday and report.
Thanks, this is on master, so not very urgent.
next prev parent reply other threads:[~2023-08-12 17:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-12 15:49 bug#65250: 30.0.50; "C-h f" is much slower on the master branch Eli Zaretskii
2023-08-12 16:57 ` Andrea Corallo
2023-08-12 17:23 ` Eli Zaretskii [this message]
2023-08-14 8:59 ` Andrea Corallo
2023-08-14 12:19 ` Eli Zaretskii
2023-08-14 14:40 ` Eli Zaretskii
2023-08-14 14:51 ` Andrea Corallo
2023-08-14 15:11 ` Eli Zaretskii
2023-08-14 15:19 ` Andrea Corallo
2023-08-14 15:45 ` Andrea Corallo
2023-08-16 8:37 ` Andrea Corallo
2023-08-16 13:12 ` Eli Zaretskii
2023-08-16 13:55 ` Andrea Corallo
2023-08-16 14:52 ` Eli Zaretskii
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=83350odvj8.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=65250@debbugs.gnu.org \
--cc=acorallo@gnu.org \
/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.