From: Ihor Radchenko <yantar92@posteo.net>
To: Michael Eliachevitch <m.eliachevitch@posteo.de>
Cc: 58687@debbugs.gnu.org
Subject: bug#58687: 29.0.50; Enabling pp-use-max-width dramatically slows down formatting of large sexps like org-persist--index
Date: Thu, 12 Jan 2023 11:27:35 +0000 [thread overview]
Message-ID: <87v8lc802g.fsf@localhost> (raw)
In-Reply-To: <871qr1cn73.fsf@posteo.de>
Michael Eliachevitch <m.eliachevitch@posteo.de> writes:
> I attached a file with the value of my `org-persist--index` expression and a file with a benchmark where I run pp on it, which took me 25s when running it with emacs -Q. Until recently my org persist index was much longer, but I pruned it a bit back when I wasn't aware what exactly caused the slowdown.
I'd like to bump this bug.
If it helps, here are the steps to reproduce:
1. Save the attached files to same folder
2. Open benchmark-pp-on-org-persist-index.el
3. M-x eval-buffer
Observed: (19.617422592 2 1.0353073050000035)
Expected: `pp' not taking ~20sec to write 15k of elisp data.
--
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>
next prev parent reply other threads:[~2023-01-12 11:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-21 12:59 bug#58687: 29.0.50; Enabling pp-use-max-width dramatically slows down formatting of large sexps like org-persist--index Michael Eliachevitch
2023-01-12 11:27 ` Ihor Radchenko [this message]
2023-01-12 13:36 ` Eli Zaretskii
2023-01-12 16:19 ` Ihor Radchenko
2023-01-12 16:33 ` Visuwesh
2023-01-12 16:39 ` Eli Zaretskii
[not found] ` <87cz7j8j5o.fsf@posteo.de>
2023-01-12 23:02 ` bug#58687: Fwd: " Michael Eliachevitch
2023-01-13 8:42 ` Eli Zaretskii
2023-01-13 9:28 ` 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=87v8lc802g.fsf@localhost \
--to=yantar92@posteo.net \
--cc=58687@debbugs.gnu.org \
--cc=m.eliachevitch@posteo.de \
/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).