From: Ted Zlatanov <tzz@lifelogs.com>
Subject: Re: gnus-registry, speed up splitting ?
Date: Tue, 02 Dec 2003 17:28:28 -0500 [thread overview]
Message-ID: <4nzneaetwz.fsf@lockgroove.bwh.harvard.edu> (raw)
In-Reply-To: <plop87n0abohju.fsf@gnu-rox.org> (Xavier Maillard's message of "Tue, 02 Dec 2003 07:33:09 +0100")
On Tue, 02 Dec 2003, zedek@gnu-rox.org wrote:
> Do you (or don't you think) that increasing
> 'gnus-registry-max-entries' value could speed-up things ? What is
> the *real* impact of setting this variable to a low-value or a
> high-value ?
Higher value = more memory and disk used, more matches will be found
Lower value = less memory and disk used, less matches will be found
Note that the registry will accumulate entries without limit during an
Emacs session. It's the *saved* registry (in ~/.gnus.registry.eld)
that will keep just the newest N entries if gnus-registry-max-entries
is set.
Ted
prev parent reply other threads:[~2003-12-02 22:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-30 22:33 Xavier Maillard
2003-12-01 21:03 ` Ted Zlatanov
2003-12-01 22:51 ` Xavier Maillard
2003-12-02 1:47 ` Ted Zlatanov
2003-12-02 6:33 ` Xavier Maillard
2003-12-02 22:28 ` Ted Zlatanov [this message]
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=4nzneaetwz.fsf@lockgroove.bwh.harvard.edu \
--to=tzz@lifelogs.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.
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).