From: Barry Margolin <barmar@alum.mit.edu>
To: help-gnu-emacs@gnu.org
Subject: Re: LISP Questions - random, random elements and memory management
Date: Thu, 19 Nov 2009 08:44:24 -0500 [thread overview]
Message-ID: <barmar-B0F0B8.08442419112009@nothing.attdns.com> (raw)
In-Reply-To: mailman.11040.1258631785.2239.help-gnu-emacs@gnu.org
In article <mailman.11040.1258631785.2239.help-gnu-emacs@gnu.org>,
Jeff Clough <jeff@chaosphere.com> wrote:
> From: Kevin Rodgers <kevin.d.rodgers@gmail.com>
> Date: Wed, 18 Nov 2009 20:03:51 -0700
>
> > The data *is* in memory. The function is zippy because nth is fast,
> > in
> > turn because cdr is fast (and implemented in C). And perhaps the cons
> > cells for the list are allocated in adjacent memory, if it is
> > constructed all at once.
> >
> > Of course you can put the data (defconst forms) and function (defun)
> > in
> > the same .el file!
>
> Um, actually I was looking for a way that would allow me to keep the
> data *out* of memory until it was needed, then toss it on the floor
> when I was done, that way I'm only eating the RAM *some* of the time
> instead of all the time. With my existing scheme, the data is in
> memory as soon as the .el file is loaded.
How about putting it in a text file that you load into a temporary
buffer when you need it? Then kill the buffer when you're done with it.
--
Barry Margolin, barmar@alum.mit.edu
Arlington, MA
*** PLEASE post questions in newsgroups, not directly to me ***
*** PLEASE don't copy me on replies, I'll read them in the group ***
next prev parent reply other threads:[~2009-11-19 13:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-18 12:54 LISP Questions - random, random elements and memory management Jeff Clough
2009-11-18 13:09 ` Jeff Clough
2009-11-19 2:53 ` Kevin Rodgers
2009-11-19 3:03 ` Kevin Rodgers
2009-11-19 11:56 ` Jeff Clough
[not found] ` <mailman.11040.1258631785.2239.help-gnu-emacs@gnu.org>
2009-11-19 13:44 ` Barry Margolin [this message]
2009-11-19 15:16 ` Jeff Clough
2009-11-20 3:52 ` Kevin Rodgers
[not found] ` <mailman.11114.1258689162.2239.help-gnu-emacs@gnu.org>
2009-11-20 6:28 ` Barry Margolin
[not found] ` <mailman.11056.1258643746.2239.help-gnu-emacs@gnu.org>
2009-11-19 17:40 ` Colin S. Miller
2009-11-19 18:57 ` Jeff Clough
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=barmar-B0F0B8.08442419112009@nothing.attdns.com \
--to=barmar@alum.mit.edu \
--cc=help-gnu-emacs@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.
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).