GNU bug report logs - #66288
29.1; Performance regression using pipe for subprocess

Previous Next

Full log

Message #59 received at 66288 <at> debbugs.gnu.org (full text, mbox):

From: Dmitry Gutov <dmitry <at> gutov.dev>
To: Eli Zaretskii <eliz <at> gnu.org>, Chris Hanson <cph <at> chris-hanson.org>
Cc: gerd.moellmann <at> gmail.com, 66288 <at> debbugs.gnu.org
Subject: Re: bug#66288: 29.1; Performance regression using pipe for subprocess
Date: Tue, 3 Oct 2023 20:42:20 +0300

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.

But if doesn't show anything conclusive, then perf is indeed the next step.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.