Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
Subject: Re: spam.el is a bit aggressive loading/saving spam-stat data
Date: Fri, 07 Mar 2003 09:55:10 -0500	[thread overview]
Message-ID: <4nadg7446p.fsf@surf.bwh.harvard.edu> (raw)
In-Reply-To: <ruoy93rntfr.fsf@billwlx.wolfram.com> (Bill White's message of "Fri, 07 Mar 2003 08:27:04 -0600")

On Fri, 07 Mar 2003, billw@wolfram.com wrote:
> It takes roughly 20-30 seconds to load my spam-stat file.  Is this a
> reasonable duration, or am I doing something wrong?  It's far too
> long to wait at each new mail retrieval.

Alex Schroeder, the spam-stat.el maintainer, might be able to answer.
Your stat file may be simply too large, and I don't think Alex has
written stats expiration code.

For large files like the stats database, even with expiration there
may be too much data, especially over NFS.  It would be nice if
spam-stat.el could use a persistent connection to a SQL database, or a
local database file (Berkeley DB, for instance).

As far as the SQL goes, I can write a simple Perl daemon that
maintains a connection to a database table and understands the basic
commands spam-stat.el needs (basically just read word stats/store word
stats).  I don't know if there's something within Emacs that could
help, so we don't have to have an external utility.

> Would it be reasonable to load the spam-stat file only when gnus
> first starts, then save it only when quitting gnus or at some other
> rare event during which I'm not waiting eagerly for something?

You could remove spam-stat-maybe-load from gnus-get-top-new-news-hook,
it's in gnus-startup-hook already if you have set spam-use-stat when
loading spam.el.

Ted



  parent reply	other threads:[~2003-03-07 14:55 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-20 18:22 David Z Maze
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 [this message]
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=4nadg7446p.fsf@surf.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).