From: Ted Zlatanov <tzz@lifelogs.com>
Cc: ding <ding@gnus.org>
Subject: Re: spam-stat regeneration notes
Date: Sun, 15 Jun 2003 14:38:48 -0400 [thread overview]
Message-ID: <4nvfv7jidj.fsf@lockgroove.bwh.harvard.edu> (raw)
In-Reply-To: <ruo7k7p4hgl.fsf@billw2lx.wolfram.com> (Bill White's message of "Fri, 13 Jun 2003 19:43:06 -0500")
On Fri, 13 Jun 2003, billw@wolfram.com wrote:
> I've been using spam-stat for about 6 months now, and noticed lately
> that spam processing was getting mightly slow - thanks (I suspect)
> to the hashbusters spammers are putting in their messages. I even
> do (spam-stat-reduce-size) when quitting gnus each day, so the thing
> was as small as possible.
Maybe we should add code that filters out terms seen only once from
the spam/ham database. Doing that once a week should work fine.
Also, spam-stat.el creates hashtables without any optimizations:
(make-hash-table :test 'equal)
maybe that could be improved. There may be many such optimization
points. I don't use spam-stat personally, but maybe you can
instrument it and see where the slowdowns are.
> So today I did my first rebuild of the spam-stat database. That's
> not bad in my book - 6 months for one constantly-growing database.
> Here's the code, which I should probably put in a function
> "spam-reset" or something.
Please do!
> - Is there an easy way to run a function over an entire directory
> tree, while specifying which dirs to include or avoid?
Maybe find-dired will help? I don't know about anything like that
built-in...
Ted
prev parent reply other threads:[~2003-06-15 18:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-14 0:43 Bill White
2003-06-14 11:57 ` François Pinard
2003-06-15 18:38 ` 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=4nvfv7jidj.fsf@lockgroove.bwh.harvard.edu \
--to=tzz@lifelogs.com \
--cc=ding@gnus.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).