all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Gerd Möllmann" <gerd.moellmann@gmail.com>
To: Dmitry Gutov <dmitry@gutov.dev>
Cc: Emacs Devel <emacs-devel@gnu.org>,  Eli Zaretskii <eliz@gnu.org>,
	Helmut Eller <eller.helmut@gmail.com>
Subject: Re: MPS: optimized build
Date: Mon, 06 May 2024 09:03:48 +0200	[thread overview]
Message-ID: <m24jbbmnfv.fsf@pro2.fritz.box> (raw)
In-Reply-To: <f2b21d9d-acf3-4bcd-a945-390d5e17bc13@gutov.dev> (Dmitry Gutov's message of "Sun, 5 May 2024 23:20:23 +0300")

Dmitry Gutov <dmitry@gutov.dev> writes:

> On 05/05/2024 09:16, Gerd Möllmann wrote:
>> 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...
>
> I've built the branch and done some measurements with
>
>   (benchmark-run 5 (project-files (project-current)))
>
> and it seems like the same or a little slower with smaller projects
> (less GC-intensive) and a stable improvement, about 5%, in in a larger
> one (more GC-intensive). Which seems good.
>
> I haven't noticed a particular change in snappiness so far, but then I
> also don't usually see this problem.

Thanks!

Interesting anecdote, maybe: I think I mentioned that have an Org file
in which GCs happened so often that it was basically unusable. This Org
file behaved much much better with MPS. Almost normal.

In the end, I found out today, that this isn't from Org, at least
directly. It is caused by bug-reference-mode, somehow. Bug submitted.



  reply	other threads:[~2024-05-06  7:03 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
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 [this message]
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

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

  git send-email \
    --in-reply-to=m24jbbmnfv.fsf@pro2.fritz.box \
    --to=gerd.moellmann@gmail.com \
    --cc=dmitry@gutov.dev \
    --cc=eliz@gnu.org \
    --cc=eller.helmut@gmail.com \
    --cc=emacs-devel@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.