unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: elisp-benchmarks
Date: Thu, 10 Feb 2022 09:52:41 +0200	[thread overview]
Message-ID: <8335krupiu.fsf@gnu.org> (raw)
In-Reply-To: <87wni3dxl1.fsf@gnus.org> (message from Lars Ingebrigtsen on Thu,  10 Feb 2022 07:50:34 +0100)

> From: Lars Ingebrigtsen <larsi@gnus.org>
> Date: Thu, 10 Feb 2022 07:50:34 +0100
> Cc: emacs-devel@gnu.org
> 
> > 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!

I'm also pleased with the speedup of bytecode, but I'm worried by the
potentially negative effect of some of those changes on memory
fragmentation: we now prevent the bytecode strings from being moved by
GC (as part of compacting strings), which could prevent Emacs from
being able to return memory to the OS, and in general increase
fragmentation.  It would be good to measure this effect somehow.  We
had in the recent past some reports about people who have the memory
footprint of their Emacs session on the order of 5 to 10 GB, allegedly
due to large blocks of memory being trapped in a way that we cannot
give them back to the OS.  I hope these changes won't make the
situation worse.



  reply	other threads:[~2022-02-10  7:52 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   ` Eli Zaretskii [this message]
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=8335krupiu.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=larsi@gnus.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).