From: Ihor Radchenko <yantar92@posteo.net>
To: Mauro Aranda <maurooaranda@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>, 53606@debbugs.gnu.org
Subject: bug#53606: 29.0.50; Very slow Customize buffer for bibtex-biblatex-entry-alist
Date: Thu, 21 Dec 2023 11:51:14 +0000 [thread overview]
Message-ID: <87a5q34vv1.fsf@localhost> (raw)
In-Reply-To: <526c4074-ee3d-8182-a4bb-7f61cc66d779@gmail.com>
Mauro Aranda <maurooaranda@gmail.com> writes:
> I focused on the format handling, since there's no need to insert the
> escape formats in the buffer. So I rearranged the 4 functions that
> handle the format to avoid it and here are the figures I got, when
> running:
> (benchmark-run 5
> (customize-option 'bibtex-biblatex-entry-alist))
>
> From master, inserting either :format or :entry-format:
> (130.200276352 291 3.1221133909999996)
>
> Without inserting it:
> (38.244185927000004 266 2.795578699)
> ...
> All data is without native compilation. I'd appreciate if someone could
> at least run it once with native compilation, with and without my patch.
I do not see much difference with native compilation:
- without the patch :: (134.779200699 247 4.294675525)
- with the patch :: (39.828912859 249 3.881637917)
But your patch is still making things faster.
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
prev parent reply other threads:[~2023-12-21 11:51 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
2023-09-18 11:07 ` Mauro Aranda
2023-12-21 11:51 ` Ihor Radchenko [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=87a5q34vv1.fsf@localhost \
--to=yantar92@posteo.net \
--cc=53606@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=maurooaranda@gmail.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).