From: Eli Zaretskii <eliz@gnu.org>
To: Dmitry Gutov <dmitry@gutov.dev>
Cc: gerd.moellmann@gmail.com, 66288@debbugs.gnu.org, cph@chris-hanson.org
Subject: bug#66288: 29.1; Performance regression using pipe for subprocess
Date: Tue, 03 Oct 2023 20:57:29 +0300 [thread overview]
Message-ID: <831qeb7fna.fsf@gnu.org> (raw)
In-Reply-To: <278d63e7-c624-4759-2c25-283e2ee60c9a@gutov.dev> (message from Dmitry Gutov on Tue, 3 Oct 2023 20:42:20 +0300)
> Date: Tue, 3 Oct 2023 20:42:20 +0300
> Cc: 66288@debbugs.gnu.org, gerd.moellmann@gmail.com
> From: Dmitry Gutov <dmitry@gutov.dev>
>
> On 03/10/2023 09:22, Eli Zaretskii wrote:
> > I think at this point, since none of the initial guesses seems to be
> > correct, running your recipe under perf and looking at the differences
> > would be our best bet? That, and bisecting the Git repository.
>
> I would start with our native profiler (M-x profiler-start ... M-x
> profiler-report). It's a bit easier to use and interpret.
Already done, see my other message.
> But if doesn't show anything conclusive, then perf is indeed the next step.
The problem seems to be in redisplay, so perf and bisecting are the
most relevant tools.
I will meanwhile try to trace the code and find what has changed.
(The usual suspect -- long-line optimizations -- seems to be off the
hook, according to my testing.)
next prev parent reply other threads:[~2023-10-03 17:57 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-01 0:57 bug#66288: 29.1; Performance regression using pipe for subprocess Chris Hanson
2023-10-01 8:39 ` Eli Zaretskii
2023-10-01 18:02 ` Chris Hanson
2023-10-02 5:02 ` Eli Zaretskii
2023-10-02 5:07 ` Eli Zaretskii
2023-10-02 17:14 ` Chris Hanson
2023-10-02 5:36 ` Eli Zaretskii
2023-10-02 18:22 ` Chris Hanson
2023-10-02 19:12 ` Gerd Möllmann
2023-10-02 19:27 ` Dmitry Gutov
2023-10-02 19:40 ` Gerd Möllmann
2023-10-02 20:15 ` Dmitry Gutov
2023-10-02 23:23 ` Chris Hanson
2023-10-03 5:06 ` Gerd Möllmann
2023-10-03 6:22 ` Eli Zaretskii
2023-10-03 6:48 ` Eli Zaretskii
2023-10-03 17:24 ` Eli Zaretskii
2023-10-03 19:12 ` Chris Hanson
2023-10-03 20:22 ` Dmitry Gutov
2023-10-03 17:42 ` Dmitry Gutov
2023-10-03 17:57 ` Eli Zaretskii [this message]
2023-10-03 20:58 ` Gregory Heytings
2023-10-03 21:26 ` Dmitry Gutov
2023-10-04 0:33 ` Chris Hanson
2023-10-04 6:52 ` Eli Zaretskii
2023-10-04 9:10 ` Gregory Heytings
2023-10-04 10:09 ` Dmitry Gutov
2023-10-04 17:55 ` Chris Hanson
2023-10-04 22:49 ` Paul Eggert
2023-10-04 22:54 ` Dmitry Gutov
2023-10-05 5:50 ` Eli Zaretskii
2023-10-05 10:48 ` Dmitry Gutov
2023-10-06 5:34 ` Eli Zaretskii
2023-10-05 5:49 ` Eli Zaretskii
2023-10-04 4:11 ` Gerd Möllmann
2023-10-04 6:55 ` Eli Zaretskii
2023-10-03 7:32 ` 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=831qeb7fna.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=66288@debbugs.gnu.org \
--cc=cph@chris-hanson.org \
--cc=dmitry@gutov.dev \
--cc=gerd.moellmann@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 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.