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: Emacs Devel <emacs-devel@gnu.org>,  Eli Zaretskii <eliz@gnu.org>,
	Helmut Eller <eller.helmut@gmail.com>
Subject: Re: MPS: optimized build
Date: Sun, 05 May 2024 03:50:44 -0400	[thread overview]
Message-ID: <yp1cyq01yuj.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <m2cyq0wzpt.fsf@pro2.fritz.box> ("Gerd Möllmann"'s message of "Sun, 05 May 2024 08:16:14 +0200")

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

> I'm using an optimized build of scratch/igc today, in an attempt to
> somehow distract myself from my sciatica. And I thought, why not write
> someting about what I'm seeing. Who knows for what it's good.
>
> This is of course macOS 14, Apple silicon.
>
> So, anecdotal observations:
>
> Survival time so far 1 hour, no crash. "Normal" usage for me, packages
> I use and so on... YMMV.
>
> I find build times surprising. 1:08 minutes with MPS (the non-debug
> version), 1:18 without MPS. I would have expected the opposite, and with
> a large difference. So much to intuition when it comes to performance,
> but that only in passing.
>
> Interactive use is, let me say, agreeable? :-)
>
> I still see pauses sometimes but I would say these are not caused by
> GC. I can see GC running BTW, with garbage-collection-messages set to
> t and I've changed igc.c to write the messages to *Messages* to have a
> better overview. So, synchronous process interaction, JSON parsing and
> what else lead to some small pauses. No surprise.
>
> In general, but I guess the wish is the father of the thought as we say
> here, Emacs seems to be, hm, snappier? Consult, vertico, corfu, ...
> completions, even typing text maybe?
>
> Would be interesting to hear from others how they perceive it...


Cool!

If you are there you might want to have a run with elisp-benchmarks [1].
IIRC one or two were GC bounded so we might see some difference 😃.

Thanks

  Andrea

[1] <https://elpa.gnu.org/packages/elisp-benchmarks.html>



  reply	other threads:[~2024-05-05  7:50 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-05  6:16 MPS: optimized build Gerd Möllmann
2024-05-05  7:50 ` Andrea Corallo [this message]
2024-05-05  8:05   ` Gerd Möllmann
2024-05-05  8:16     ` Andrea Corallo
2024-05-06 13:44   ` Helmut Eller
2024-05-06 20:28     ` Andrea Corallo
2024-05-07  7:13     ` MPS: bignums (was: MPS: optimized build) Helmut Eller
2024-05-07  7:21       ` MPS: bignums Gerd Möllmann
2024-05-07  8:15       ` MPS: bignums (was: MPS: optimized build) Mattias Engdegård
2024-05-07  9:06         ` MPS: bignums Helmut Eller
2024-05-07  9:27           ` Gerd Möllmann
2024-05-07  9:48           ` Mattias Engdegård
2024-05-07 12:17             ` Gerd Möllmann
2024-05-07 16:33             ` Helmut Eller
2024-05-07 16:38               ` Mattias Engdegård
2024-05-08 12:59               ` Helmut Eller
2024-05-08 13:08                 ` Gerd Möllmann
2024-05-08 13:13                   ` Helmut Eller
2024-05-08 13:14                     ` Gerd Möllmann
2024-05-05 20:20 ` MPS: optimized build Dmitry Gutov
2024-05-06  7:03   ` Gerd Möllmann
2024-05-06 11:49     ` Eli Zaretskii
2024-05-06 15:16       ` Dmitry Gutov
2024-05-06 15:17     ` Dmitry Gutov

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=yp1cyq01yuj.fsf@fencepost.gnu.org \
    --to=acorallo@gnu.org \
    --cc=eliz@gnu.org \
    --cc=eller.helmut@gmail.com \
    --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).