From: Eli Zaretskii <eliz@gnu.org>
To: Tomas Hlavaty <tom@logand.com>
Cc: emacs-devel@gnu.org
Subject: Re: funcall consing
Date: Fri, 31 Dec 2021 14:33:47 +0200 [thread overview]
Message-ID: <83fsq9gdhw.fsf@gnu.org> (raw)
In-Reply-To: <87ee5tm422.fsf@logand.com> (message from Tomas Hlavaty on Fri, 31 Dec 2021 12:01:09 +0100)
> From: Tomas Hlavaty <tom@logand.com>
> Date: Fri, 31 Dec 2021 12:01:09 +0100
>
> in order to optimize some elisp code, I am trying to understand where my
> consing comes from. So far it looks like that my assumption about the
> cause of consing are wrong and that the cause of consing is funcall. Is
> that plausible? I am seeing similar results like this (lexical-binding,
> also byte compiled):
>
> (benchmark-run 10 (dotimes (i 100000) (1+ i)))
> ;;(2.720941123 40 1.7525918699999998)
> (let ((x (lambda (i) (1+ i)))) (benchmark-run 10 (dotimes (i 100000) (funcall x i))))
> ;;(4.9373091140000005 80 3.4835688719999958)
>
> i.e. funcall conses a lot and introduces cca double performance penalty.
What do you mean by "consing" in this context, and what is your
evidence for "consing" in the above example? Is that only the
performance degradation, or is that something else?
next prev parent reply other threads:[~2021-12-31 12:33 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 [this message]
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
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=83fsq9gdhw.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@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.