bug#66288: 29.1; Performance regression using pipe for subprocess

[Dmitry Gutov]

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.