unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Andrea Corallo <acorallo@gnu.org>
To: "Gerd Möllmann" <gerd.moellmann@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>,  emacs-devel@gnu.org
Subject: Re: MPS experiment successful
Date: Thu, 18 Apr 2024 05:14:19 -0400	[thread overview]
Message-ID: <yp1cyqnjams.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <m2pluogiy5.fsf@Pro.fritz.box> ("Gerd Möllmann"'s message of "Wed, 17 Apr 2024 16:30:42 +0200")

Gerd Möllmann <gerd.moellmann@gmail.com> writes:

> Eli Zaretskii <eliz@gnu.org> writes:
>
>>> That's all. There is nothing more. And I'm currently undecided how to
>>> proceed with this.
>>
>> The next step would be to push a feature branch into the Emacs Git
>> repository and let people try the branch on the other supported
>> platforms.  If the code is not yet mature enough for that, please
>> suggest how to get from here to there.
>
> I think technically it could be done, but there are some things that
> would need to be done. From the top of my head:
>
> - CL packages vs. obarrays (I do have packages but no obarrays)
> - Handling of pure space
> - Handling the new JSON stuff, which I don't have in my branch, I think.
> - ...
>
> And then of course the general work of getting a branch from a what is
> basically a fork back to the forked repo, which I'm not so sure how to
> go about that.
>
> But my undecidedness comes more from what could come after that. I'm not
> sure how willing I am to invest what can be years to get things
> finished, esp. if no one else starts working on it. Had that one time
> too often in the 90s, some might remember ;-).
>
>> Would you like to describe in a few words what would be the advantages
>> and disadvantages of this GC for Emacs?
>
> Advantages for users:
>
> For the user it means the final end to GC pauses. MPS runs in a
> different thread wich can be in a different core.
>
> What MPS means for the overall speed of Emacs I find impossible to say.
> MPS doesn't seem to be slow at all though, although some slowdown can be
> expected in the client because of thread-safe allocations.
>
> Example for a confusing fact that I noticed today:
>
> Full build without MPS, -O0, checking
>
> real	26:20.01
> user	1:32:15.54
> sys	3:20.74
>
> Same build with debug MPS (-lmps-debug)
>
> real	14:07.90
> user	44:17.94
> sys	3:15.99
>
> That's on an 2,3 GHz Quad-Core Intel Core i7, 16G RAM, SSD. 🤷

Hi Gerd,

sounds very interesting.  I think we'll need more performance figures
especially on non debug builds in the future to better undesrtand this.

OTOH even in case it proves to be a tiny bit slower having no pauses is
a big plus.

  Andrea



  parent reply	other threads:[~2024-04-18  9:14 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-17 10:46 MPS experiment successful Gerd Möllmann
2024-04-17 12:22 ` Björn Bidar
     [not found] ` <87cyqo89gk.fsf@>
2024-04-17 12:35   ` Björn Bidar
2024-04-17 13:09 ` Eli Zaretskii
2024-04-17 14:30   ` Gerd Möllmann
2024-04-17 15:49     ` Eli Zaretskii
2024-04-17 16:29       ` Gerd Möllmann
2024-04-17 17:51         ` Eli Zaretskii
2024-04-17 18:34           ` Gerd Möllmann
2024-04-17 19:21             ` Eli Zaretskii
2024-04-17 18:41       ` Gerd Möllmann
2024-04-17 19:23         ` Eli Zaretskii
2024-04-17 19:51           ` Gerd Möllmann
2024-04-17 23:45             ` Dmitry Gutov
2024-04-18  4:27               ` Gerd Möllmann
2024-04-18  5:08             ` Eli Zaretskii
2024-04-18  8:57               ` Gerd Möllmann
2024-04-18 19:18                 ` Gerd Möllmann
2024-04-17 23:48     ` Dmitry Gutov
2024-04-18  4:31       ` Gerd Möllmann
2024-04-18  9:14     ` Andrea Corallo [this message]
     [not found] ` <661fbf1d.050a0220.936ef.ee84SMTPIN_ADDED_BROKEN@mx.google.com>
2024-04-17 13:26   ` Gerd Möllmann
     [not found] ` <661fc22e.170a0220.18fe3.c635SMTPIN_ADDED_BROKEN@mx.google.com>
2024-04-17 13:33   ` Gerd Möllmann
2024-04-17 14:22     ` Björn Bidar
     [not found]     ` <661fdb15.5d0a0220.4bfec.1ac8SMTPIN_ADDED_BROKEN@mx.google.com>
2024-04-17 14:34       ` Gerd Möllmann

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=yp1cyqnjams.fsf@fencepost.gnu.org \
    --to=acorallo@gnu.org \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).