From: Eli Zaretskii <eliz@gnu.org>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: 58687@debbugs.gnu.org, m.eliachevitch@posteo.de
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 18:39:35 +0200 [thread overview]
Message-ID: <83zganaerc.fsf@gnu.org> (raw)
In-Reply-To: <87cz7j9146.fsf@localhost> (message from Ihor Radchenko on Thu, 12 Jan 2023 16:19:37 +0000)
> From: Ihor Radchenko <yantar92@posteo.net>
> Cc: m.eliachevitch@posteo.de, 58687@debbugs.gnu.org
> Date: Thu, 12 Jan 2023 16:19:37 +0000
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > 40041 85% - pp
> > 40041 85% - pp-to-string
> > 40041 85% - pp-emacs-lisp-code
> > 40028 85% - pp--insert-lisp
> > 40028 85% - pp--format-list
> > 40028 85% - pp--insert
> > 38710 82% - pp--insert-lisp
> > 38710 82% - pp--format-list
>
> So, the current `pp' implementation is re-parsing from bob for every
> nested list inside sexp.
Not "the current 'pp'", but the implementation for this optional
behavior.
> This is quadratic scaling, and, as the repro demonstrates, the time
> goes up very quickly. Is the new option usable at all in practice?
Maybe only for small code fragments.
next prev parent reply other threads:[~2023-01-12 16:39 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
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 [this message]
[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=83zganaerc.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=58687@debbugs.gnu.org \
--cc=m.eliachevitch@posteo.de \
--cc=yantar92@posteo.net \
/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).