From: Mauro Aranda <maurooaranda@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 53606@debbugs.gnu.org
Subject: bug#53606: 29.0.50; Very slow Customize buffer for bibtex-biblatex-entry-alist
Date: Sun, 10 Sep 2023 09:41:27 -0300 [thread overview]
Message-ID: <21ff8522-0f11-5786-3113-aa79419957d9@gmail.com> (raw)
In-Reply-To: <83edj6s404.fsf@gnu.org>
On 10/9/23 07:43, Eli Zaretskii wrote:
>> Date: Sun, 10 Sep 2023 06:49:29 -0300
>> Cc: 53606@debbugs.gnu.org
>> From: Mauro Aranda <maurooaranda@gmail.com>
>>
>> On 10/9/23 02:01, Eli Zaretskii wrote:
>> > Could you please profile this slow operation and post the completely
>> > unfolded profile? I think we should try to understand what exactly
>> > takes so much time in this case.
>>
>> Here it is. I also attach the result of C-x C-w in the report buffer,
>> just in case.
>
> So the hot spot seems to be widget-checklist-add-item, is that right?
I think so. The checklist widgets were my first suspects, since
creating them is rather slow.
> And inside that widget-create-child and widget-apply?
I don't think those functions could be the bottleneck. Most likely it
is the widget-default-create function that those functions end up
calling. So yes, widget-default-create in general, and
widget-checklist-value-create in particular should be investigated for
speeding them up, but I don't have any ideas at the moment.
next prev parent reply other threads:[~2023-09-10 12:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-28 15:03 bug#53606: 29.0.50; Very slow Customize buffer for bibtex-biblatex-entry-alist Lars Ingebrigtsen
2023-09-09 22:23 ` Mauro Aranda
2023-09-09 22:51 ` Mauro Aranda
2023-09-10 5:01 ` Eli Zaretskii
2023-09-10 9:49 ` Mauro Aranda
2023-09-10 10:43 ` Eli Zaretskii
2023-09-10 10:50 ` Ihor Radchenko
2023-09-10 12:41 ` Mauro Aranda [this message]
2023-09-18 11:07 ` Mauro Aranda
2023-12-21 11:51 ` Ihor Radchenko
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=21ff8522-0f11-5786-3113-aa79419957d9@gmail.com \
--to=maurooaranda@gmail.com \
--cc=53606@debbugs.gnu.org \
--cc=eliz@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 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).