From: Chris Green <cmg@dok.org>
Subject: Re: emulating mozilla's Label command
Date: Fri, 16 Apr 2004 12:30:39 -0400 [thread overview]
Message-ID: <m28ygvzxzk.fsf@catbert.dok.org> (raw)
In-Reply-To: <4nk70g9dom.fsf@b2-25-3.bwh.harvard.edu> (Ted Zlatanov's message of "Fri, 16 Apr 2004 10:53:45 -0400")
Ted Zlatanov <tzz@lifelogs.com> writes:
> The registry will need reverse mappings to do this, which will use
> memory and CPU. So it should be optional, and if it's off then it
> will cost the user more CPU to retrieve the reverse mapping (but the
> CPU and memory costs will be localized instead of distributed).
> There should be four settings for caching:
>
> t (build cache ASAP and keep it)
> nil (never, only build cache when needed and release it afterwards)
> 'opportunistic (cache is built when needed and reused later)
> '(...) (list of types of extra data that should be cached, all others
> are built when needed)
Ahh that would be a nice generic feature. I was sitting here thinking
of "oh it wouldn't be hard to copy the hash table stuff to make a
reverse map for labels"..
I'm not sure what nil means here. The purpose of that variable is to
keep memory down at the potential expense of CPU. In that mode, a
each cache-reverse lookup would have to do an O(N) search.
Put another way:
Is the difference between 'opportunistic and nil:
1) saving to disk or
2) creation of an in-memory cache at all
> What do you think?
Seems like a great solution to me.
--
Chris Green <cmg@dok.org>
To err is human, to moo bovine.
next prev parent reply other threads:[~2004-04-16 16:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-08 14:02 Chris Green
2004-04-08 15:59 ` Wes Hardaker
2004-04-10 10:40 ` Sacha Chua
2004-04-10 14:14 ` Wes Hardaker
2004-04-08 21:29 ` Simon Josefsson
2004-04-12 15:03 ` Ted Zlatanov
2004-04-12 16:46 ` Kai Grossjohann
2004-04-13 15:30 ` Ted Zlatanov
2004-04-13 19:14 ` Chris Green
2004-04-15 19:40 ` Ted Zlatanov
2004-04-15 20:01 ` Chris Green
2004-04-16 14:53 ` Ted Zlatanov
2004-04-16 16:30 ` Chris Green [this message]
2004-04-16 20:10 ` Ted Zlatanov
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=m28ygvzxzk.fsf@catbert.dok.org \
--to=cmg@dok.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 NNTP newsgroup(s).