From: "Mattias Engdegård" <mattiase@acm.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: elisp-benchmarks
Date: Thu, 10 Feb 2022 22:53:06 +0100 [thread overview]
Message-ID: <BAAD6C3D-6CD2-4D09-A07E-0EC0FEF08DB6@acm.org> (raw)
In-Reply-To: <jwviltmsma7.fsf-monnier+emacs@gnu.org>
10 feb. 2022 kl. 17.51 skrev Stefan Monnier <monnier@iro.umontreal.ca>:
> And here's `emacs-26` (i.e. commit 7497ee44b471f69ce59d131a6dece261e871534f)
Thank you! Normalised to the first version where each benchmark result appears, we have (excluding GC):
| | 26 | 27 | 28 | pre sympos | sympos | master |
|--------------------+------+------+------+------------+--------+--------|
| bubble | 1.00 | 0.81 | 0.54 | 0.62 | 0.58 | 0.46 |
| bubble-no-cons | 1.00 | 0.87 | 0.75 | 0.77 | 0.78 | 0.63 |
| bytecomp | 1.00 | 0.94 | 1.00 | 1.07 | 1.13 | 1.06 |
| dhrystone | 1.00 | 0.91 | 0.82 | 0.83 | 0.86 | 0.66 |
| eieio | 1.00 | 0.98 | 0.95 | 1.04 | 1.03 | 0.87 |
| fibn | 1.00 | 0.86 | 0.75 | 0.75 | 0.75 | 0.52 |
| fibn-named-let | | | 1.00 | 1.03 | 1.01 | 0.70 |
| fibn-rec | 1.00 | 1.14 | 1.00 | 1.02 | 1.04 | 0.68 |
| fibn-tc | 1.00 | 1.05 | 0.96 | 0.99 | 1.00 | 0.59 |
| flet | 1.00 | 1.23 | 0.88 | 0.91 | 0.96 | 0.62 |
| inclist | 1.00 | 1.36 | 0.79 | 0.78 | 0.84 | 0.76 |
| inclist-type-hints | 1.00 | 1.40 | 0.60 | 0.59 | 0.64 | 0.58 |
| listlen-tc | 1.00 | 0.97 | 0.89 | 0.91 | 0.92 | 0.67 |
| map-closure | 1.00 | 1.14 | 1.04 | 1.04 | 1.06 | 0.72 |
| nbody | 1.00 | 0.95 | 0.82 | 0.84 | 0.81 | 0.71 |
| pack-unpack | | | 1.00 | 1.04 | 1.03 | 0.83 |
| pack-unpack-old | 1.00 | 0.89 | 0.49 | 0.52 | 0.52 | 0.47 |
| pcase | 1.00 | 0.86 | 0.72 | 0.74 | 0.64 | 0.63 |
| pidigits | | 1.00 | 1.06 | 1.15 | 1.07 | 0.99 |
| scroll | | | 1.00 | 1.05 | 1.02 | 1.09 |
| smie | 1.00 | 0.86 | 0.78 | 0.77 | 0.79 | 0.78 |
(The pidigits result was omitted from Emacs 26 because it didn't make much sense.)
The bytecomp benchmark is mobile -- it does more work (and generates better code) now than in earlier versions.
Not sure how comparable scroll is, but it's probably a difficult thing to measure.
next prev parent reply other threads:[~2022-02-10 21:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-09 22:19 elisp-benchmarks Stefan Monnier
2022-02-10 6:50 ` elisp-benchmarks Lars Ingebrigtsen
2022-02-10 7:52 ` elisp-benchmarks Eli Zaretskii
2022-02-10 12:12 ` elisp-benchmarks Mattias Engdegård
2022-02-10 14:13 ` elisp-benchmarks Stefan Monnier
2022-02-10 14:18 ` elisp-benchmarks Stefan Monnier
2022-02-10 16:51 ` elisp-benchmarks Stefan Monnier
2022-02-10 21:53 ` Mattias Engdegård [this message]
2022-02-10 22:31 ` elisp-benchmarks Stefan Monnier
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=BAAD6C3D-6CD2-4D09-A07E-0EC0FEF08DB6@acm.org \
--to=mattiase@acm.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).