unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Andrea Corallo <acorallo@gnu.org>
To: Helmut Eller <eller.helmut@gmail.com>
Cc: "Gerd Möllmann" <gerd.moellmann@gmail.com>,
	"Emacs Devel" <emacs-devel@gnu.org>,
	"Eli Zaretskii" <eliz@gnu.org>
Subject: Re: MPS: optimized build
Date: Mon, 06 May 2024 16:28:09 -0400	[thread overview]
Message-ID: <yp1msp2znvq.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <87bk5j12dc.fsf@gmail.com> (Helmut Eller's message of "Mon, 06 May 2024 15:44:31 +0200")

Helmut Eller <eller.helmut@gmail.com> writes:

> On Sun, May 05 2024, Andrea Corallo wrote:
>
>> [1] <https://elpa.gnu.org/packages/elisp-benchmarks.html>
>
> I ran those with:

Thanks!

>   emacs -Q -batch
>    -l ~/.emacs.d/elpa/elisp-benchmarks-1.14/elisp-benchmarks.el
>    -eval '(elisp-benchmarks-run nil nil 1)' 2>&1 |tee /tmp/mps-result.txt
>
> the results are below.
>
> I had to disable the pidigits program because the MPS version ate all
> memory and began to swap.  There's probably something wrong with
> bignums.

That's a pity, AFAIR pidigits was the one heavy on GC.

> For most programs the two versions are relatively close, except for
> nbody where the old GC does much better.  The nbody program seems to
> involve floating point arithmetic.  Maybe there's something wrong with
> floats too.  Or maybe the extra header costs so much.

Few others shows a noticeable performance slowdown, (assuming it's not
just noise of course).  There time to look into what's really going on
tho :)

Thanks

  Andrea



  reply	other threads:[~2024-05-06 20:28 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 [this message]
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=yp1msp2znvq.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).