From: David Z Maze <dmaze@MIT.EDU>
Subject: spam.el is a bit aggressive loading/saving spam-stat data
Date: Thu, 20 Feb 2003 13:22:04 -0500 [thread overview]
Message-ID: <y68heayg6cz.fsf@multics.mit.edu> (raw)
spam.el with spam-stat seems to work fairly well for me (certainly, as
well as ifile ever did). The one thing I was hoping for out of it,
though, was that since the scoring information lived with the Emacs
process, I wouldn't take a performance hit for reading and parsing a
500K text file for every incoming message. The code in spam.el seems
to be on the aggressive side loading and saving, though: spam-split,
which is called for every message, calls (spam-stat-load), and both of
the spam-stat-register functions end by calling (spam-stat-save).
Is it straightforward to change this so that (spam-stat-load) happens
once when Gnus starts up, and then (spam-stat-save) is called, say,
along with everything else when I press 's' from the group buffer?
I'd think this would noticably improve splitting performance for me.
Thanks,
--
David Maze dmaze@mit.edu http://www.mit.edu/~dmaze/
"Theoretical politics is interesting. Politicking should be illegal."
-- Abra Mitchell
next reply other threads:[~2003-02-20 18:22 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-20 18:22 David Z Maze [this message]
2003-02-21 8:16 ` Niklas Morberg
2003-02-21 15:14 ` Ted Zlatanov
2003-02-21 20:25 ` David Z Maze
2003-02-21 20:49 ` Ted Zlatanov
2003-02-21 21:06 ` David Z Maze
2003-02-21 23:58 ` Alex Schroeder
2003-02-24 21:53 ` Ted Zlatanov
2003-02-26 2:23 ` David Z Maze
2003-02-26 21:15 ` Ted Zlatanov
2003-03-01 13:26 ` David Z Maze
2003-03-01 15:08 ` Ted Zlatanov
2003-03-02 23:49 ` David Z Maze
2003-03-06 13:22 ` Niklas Morberg
2003-03-06 15:39 ` Ted Zlatanov
2003-03-07 14:27 ` Bill White
2003-03-07 14:38 ` Niklas Morberg
2003-03-07 15:13 ` Bill White
2003-03-10 8:05 ` Niklas Morberg
2003-03-11 12:53 ` Bill White
2003-03-07 14:55 ` Ted Zlatanov
2003-03-07 22:55 ` A.J. Rossini
2003-03-08 0:49 ` Alex Schroeder
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=y68heayg6cz.fsf@multics.mit.edu \
--to=dmaze@mit.edu \
/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).