From: Xavier Maillard <zedek@gnu-rox.org>
Subject: Re: gnus-registry, speed up splitting ?
Date: Tue, 02 Dec 2003 07:33:09 +0100 [thread overview]
Message-ID: <plop87n0abohju.fsf@gnu-rox.org> (raw)
In-Reply-To: <4n8ylwuh1b.fsf@lockgroove.bwh.harvard.edu> (Ted Zlatanov's message of "Mon, 01 Dec 2003 20:47:44 -0500")
Ted Zlatanov <tzz@lifelogs.com> disait récemment que :
> On Mon, 01 Dec 2003, zedek@gnu-rox.org wrote:
>
>> Ted Zlatanov <tzz@lifelogs.com> disait récemment que :
>>
>>> On Sun, 30 Nov 2003, zedek@gnu-rox.org wrote:
>>>
>>>> Since I use gnus-registry stuff, it seems to me that my gnus is
>>>> much more responsive especially when splitting.
>>>>
>>>> Does anybody have the same impression or is it the 'fault' of my
>>>> new laptop ?
>>>
>>> Do you mean "less responsive"? I'll assume so.
>>
>> No I had the impression (but I may be wrong), that it was quicker ;)
>
> OK, your subject header was misleading, it seemed you want me to
> "speed up splitting." I undertsand now. Maybe the registry is
> finding matches sooner, so the rest of the spam checks don't need to
> be made?
Yeah maybe. 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 ?
> As you can see, I can provide plausible reasons for why the registry
> would make things slower or faster :) It's not a O(1) operation,
> that's the bottom line. The speed depends on too many things.
Yes I can understand that but anyway, 2 months ago, it didn't work at
all for me (remember my posts) and now, it is just great ;)
> Ted
zeDek
next prev parent reply other threads:[~2003-12-02 6:33 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 [this message]
2003-12-02 22:28 ` 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=plop87n0abohju.fsf@gnu-rox.org \
--to=zedek@gnu-rox.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).