all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Chris Hanson <cph@chris-hanson.org>
Cc: 66288@debbugs.gnu.org
Subject: bug#66288: 29.1; Performance regression using pipe for subprocess
Date: Sun, 01 Oct 2023 11:39:49 +0300	[thread overview]
Message-ID: <83ttra91nu.fsf@gnu.org> (raw)
In-Reply-To: <b62a38be-e5eb-4a52-94c9-f3f314c0a777@chris-hanson.org> (message from Chris Hanson on Sat, 30 Sep 2023 20:57:31 -0400)

> Date: Sat, 30 Sep 2023 20:57:31 -0400
> From: Chris Hanson <cph@chris-hanson.org>
> 
> When using "xscheme.el" to start and interact with MIT/GNU Scheme in a
> subprocess, the performance significantly degraded in Emacs 29.1.  It
> worked well in older releases.
> 
> Here is a recipe:
> 
>      emacs -Q
>      M-x load-library RET xscheme RET
>      M-x run-scheme RET
> 
>      and see how slowly the process output is printed as Scheme starts.
>      Compare this to Emacs 28.2 or earlier.

Please post the comparison as you see it on your system, preferably in
quantitative terms (e.g., time it takes to read and process some chunk
of text in both versions), and using the same version of MIT/GNU
Scheme.

FWIW, I see no changes in xscheme.el between v28.1 and v29.1, except
some minor aesthetic changes and renames of functions.  So I wonder
how come you see a significant slowdown.





  reply	other threads:[~2023-10-01  8:39 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 [this message]
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
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=83ttra91nu.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=66288@debbugs.gnu.org \
    --cc=cph@chris-hanson.org \
    /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.