all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "John Wiegley" <johnw@gnu.org>
Cc: 62975@debbugs.gnu.org
Subject: bug#62975: 29.0.90; Forking processes on macOS has become very slow in Emacs 29
Date: Thu, 20 Apr 2023 21:58:09 +0300	[thread overview]
Message-ID: <83sfcu4bzy.fsf@gnu.org> (raw)
In-Reply-To: <m2o7nixup7.fsf@newartisans.com> (johnw@gnu.org)

> From: "John Wiegley" <johnw@gnu.org>
> Date: Thu, 20 Apr 2023 11:41:24 -0700
> 
> I noticed after upgrading to 29.0.90 that Emacs felt very sluggish. I was able
> to track this down to slow forking behavior, such as what happened in Emacs 26
> days. As an example, I started with emacs -Q and then loaded magit and used it
> to check for changes in one of my local repositories. These are the timings
> for just hitting 'g':
> 
>    28.2            Refreshing magit...done (0.298s, cached 11/25 (44%))
>    28.2-Macport    Refreshing magit...done (0.140s, cached 6/16 (38%))
>    29.0.90         Refreshing magit...done (1.495s, cached 11/25 (44%))
> 
> As you can see, with identical configuration (-Q) and the same Git project,
> refreshing takes 7 times longer with Emacs 29 than it did with Emacs 28.

Thanks.

Can someone else who uses Emacs 29 on macOS reproduce this regression
in performance relative to Emacs 28?





  reply	other threads:[~2023-04-20 18:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-20 18:41 bug#62975: 29.0.90; Forking processes on macOS has become very slow in Emacs 29 John Wiegley
2023-04-20 18:58 ` Eli Zaretskii [this message]
2023-04-22  7:06   ` M. Ian Graham
2023-04-22  7:53     ` Eli Zaretskii
2023-04-22  8:59       ` M. Ian Graham
2023-04-25 15:59     ` Daniel Martín via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-16 12:54 ` Alan Third

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=83sfcu4bzy.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=62975@debbugs.gnu.org \
    --cc=johnw@gnu.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.