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

On Thu Mar 06 2003 at 09:39, Ted Zlatanov <tzz@lifelogs.com> said:

> On Thu, 06 Mar 2003, niklas.morberg@axis.com wrote:
>> I just noticed that the spam-stat data is loaded when moving
>> messages, which seems a bit unnecessary. The reason is that
>> gnus-summary-move-article makes a call to
>> gnus-group-get-new-news-this-group which in turn loads the
>> spam-stat file.
>> 
>> Would it be possible to get rid of this as well?
>
> I added a gnus-get-top-new-news-hook which is NOT invoked by
> gnus-group-get-new-news-this-group to get around this, only by
> gnus-get-new-news.  I also moved the spam.el stat loading hook to
> the gnus-get-top-new-news-hook.  If anyone has a problem with that
> new hook, let me know (but seriously, can Gnus ever have enough
> hooks? :)

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.

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?

Cheers -

bw
-- 
Bill White . billw@wolfram.com . http://members.wri.com/billw
"No ma'am, we're musicians."




  reply	other threads:[~2003-03-07 14:27 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 [this message]
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=ruoy93rntfr.fsf@billwlx.wolfram.com \
    --to=billw@wolfram.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).