From: Lars Ingebrigtsen <larsi@gnus.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: elisp-benchmarks
Date: Thu, 10 Feb 2022 07:50:34 +0100 [thread overview]
Message-ID: <87wni3dxl1.fsf@gnus.org> (raw)
In-Reply-To: <jwv5ypn7l9z.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Wed, 09 Feb 2022 17:19:28 -0500")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
> These result suggest that the symbol-with-pos changes don't introduce
> a significant slowdown, even for the bytecompiler.
Well, that's good news. 😀
> And we see that Matthias's recent improvements to the bytecode
> interpreter do make a quite significant difference on several of those
> microbenchmarks ;-), and also on the bytecompiler benchmark (offsetting
> the extra work needed for the symbol-with-positions)
Looks like Matthias's work has made a significant positive impact on
virtually all the tests. Great work, Matthias!
> tho they don't make much of a difference when it comes to
> scrolling(with-jit-lock) or when it comes to reindenting code with
> SMIE :-)
Darn.
> The >10% slowdown recently seen on the test suite is still a mystery
> waiting for someone to figure out what's going on.
Yes, but it sounded like Alan was chasing down oddities in
byte-compiling the ert tests, so hopefully we'll have an answer soonish.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2022-02-10 6:50 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 ` Lars Ingebrigtsen [this message]
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 ` elisp-benchmarks Mattias Engdegård
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=87wni3dxl1.fsf@gnus.org \
--to=larsi@gnus.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).