From: John Wiegley <jwiegley@gmail.com>
To: michael schuldt <mbschuldt@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>, Ken Raeburn <raeburn@raeburn.org>,
rms@gnu.org, emacs-devel@gnu.org
Subject: Re: Should we land Lisp reader optimizations?
Date: Wed, 21 Jun 2017 23:25:41 -0700 [thread overview]
Message-ID: <m2k244fsii.fsf@newartisans.com> (raw)
In-Reply-To: <CABhu7fUFyeYX_cYwzDxB7LdCtRsoWrjua3XRBvt2b7jrYj9Ctg@mail.gmail.com> (michael schuldt's message of "Wed, 21 Jun 2017 19:56:06 -0700")
>>>>> "ms" == michael schuldt <mbschuldt@gmail.com> writes:
ms> But in either case Ken seems to make it clear that it does not really
ms> matter - GC overhead is small when reading normal files and already
ms> minimized for the big .elc read
And in fact, the GC can make things faster, by quickly freeing temporarily
allocated memory that can be reused in a subsequent loop iteration. Although
it does take "work" to walk the heap and free objects, sometimes this work is
less than freshly allocating new temporary blocks at ever-new places on the
heap.
--
John Wiegley GPG fingerprint = 4710 CF98 AF9B 327B B80F
http://newartisans.com 60E1 46C4 BD1A 7AC1 4BA2
next prev parent reply other threads:[~2017-06-22 6:25 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-19 16:58 Should we land Lisp reader optimizations? Eli Zaretskii
2017-06-20 7:08 ` Ken Raeburn
2017-06-20 10:12 ` Ken Raeburn
2017-06-20 15:25 ` Eli Zaretskii
2017-06-20 15:39 ` Clément Pit-Claudel
2017-06-20 16:06 ` Paul Eggert
2017-06-20 23:12 ` John Wiegley
2017-06-21 2:50 ` michael schuldt
2017-06-21 10:07 ` Ken Raeburn
2017-06-21 17:41 ` Eli Zaretskii
2017-06-22 1:58 ` Richard Stallman
2017-06-22 2:56 ` michael schuldt
2017-06-22 6:25 ` John Wiegley [this message]
2017-06-22 13:26 ` Stefan Monnier
2017-06-22 1:57 ` Richard Stallman
2017-06-21 9:46 ` Ken Raeburn
2017-06-21 17:56 ` Eli Zaretskii
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=m2k244fsii.fsf@newartisans.com \
--to=jwiegley@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=mbschuldt@gmail.com \
--cc=raeburn@raeburn.org \
--cc=rms@gnu.org \
/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).