all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: rms@gnu.org
Cc: tom@logand.com, emacs-devel@gnu.org
Subject: Re: funcall consing
Date: Sat, 01 Jan 2022 09:26:20 +0200	[thread overview]
Message-ID: <83pmpbgbmr.fsf@gnu.org> (raw)
In-Reply-To: <E1n3WIU-0004ML-B1@fencepost.gnu.org> (message from Richard Stallman on Fri, 31 Dec 2021 23:47:14 -0500)

> From: Richard Stallman <rms@gnu.org>
> Cc: andpuke@foxmail.com, tom@logand.com, emacs-devel@gnu.org
> Date: Fri, 31 Dec 2021 23:47:14 -0500
> 
>   > > The `80' indicats the GC has been invoked 80 times. That is the direct
>   > > indication of "consing".
> 
>   > Why are you saying that the number of times GC has been invoked is the
>   > direct indication of consing?
> 
> It used to be the case, and maybe still is that the decision on
> whether to call GC on any given occasion was controlled by how much
> space had been allocated since the previous GC.

It is still the case.  But the details matter in this case: we
actually call GC in some strategic points, regardless of how much
consing was made, and if it decides that not enough consing has
happened since the last call, it does nothing and immediately returns;
such "do-nothing" GC cycles then aren't counted in gcs-done.

> If that is true nowadays, then calling GC roughly measures the
> amount of consing.

Not necessarily.  If you write Lisp that rarely calls the functions
which call GC, then GC won't have enough opportunities to check how
much consing has happened.  This would produce fewer GC cycles,
although each cycle might collect more garbage.

Note that one of the examples posted by the OP does exactly twice GC
cycles that the other.  Which leads me to believe it had twice more
opportunities for checking how much consing was done.

So I think the caveat not to put too much faith in the _number_ of GC
cycles is still something important to keep in mind.



  reply	other threads:[~2022-01-01  7:26 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-31 11:01 funcall consing Tomas Hlavaty
2021-12-31 12:33 ` Eli Zaretskii
2021-12-31 15:09   ` LdBeth
2021-12-31 17:00     ` Tomas Hlavaty
2021-12-31 18:42     ` Eli Zaretskii
2022-01-01  4:47       ` Richard Stallman
2022-01-01  7:26         ` Eli Zaretskii [this message]
2022-01-02 13:30           ` Tomas Hlavaty
2022-01-02 14:46             ` Eli Zaretskii
2022-01-02 15:59               ` Tomas Hlavaty
2022-01-02 18:53             ` Stefan Monnier
2022-01-01  4:51       ` LdBeth
2022-01-01  7:28         ` Eli Zaretskii
2022-01-01 17:05           ` Stefan Monnier
2022-01-01 17:21             ` Eli Zaretskii
2021-12-31 14:27 ` LdBeth
2021-12-31 16:56   ` Tomas Hlavaty

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=83pmpbgbmr.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=rms@gnu.org \
    --cc=tom@logand.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 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.