Gnus development mailing list
 help / color / mirror / Atom feed
From: Reiner Steib <4.uce.03.r.s@nurfuerspam.de>
Subject: Re: Spam processing slows down group exit
Date: Fri, 02 Jan 2004 19:40:55 +0100	[thread overview]
Message-ID: <v9r7yikxc8.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <4nznd6jptc.fsf@collins.bwh.harvard.edu>

On Fri, Jan 02 2004, Ted Zlatanov wrote:

> On Thu, 01 Jan 2004, 4.uce.03.r.s@nurfuerspam.de wrote:
>
>> I found that the group and topic parameters (spam/ham) are
>> calculated[1] for *every article* rather than once for each group
>> exit.
[...]
> Fixed in CVS, take a look.

Thanks.  It's fine now.

> I didn't bother with a global cache, because it would be much
> optimizing for a small gain, 

Yes, I agree.

>> Why is `spam-ham-copy-or-move-routine' called in the first place?  I
>> have not requested any spam processing in this group.
>
> It's called from spam-summary-prepare-exit, can you check why it's
> being invoked in your case in particular?  It should only be called
> here (through the spam-ham-{copy,move}-routine proxies):

It seems it isn't called anymore with your change.

Bye, Reiner.
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo--- PGP key available via WWW   http://rsteib.home.pages.de/




      reply	other threads:[~2004-01-02 18:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-30  3:58 Profiling Lars Magne Ingebrigtsen
2003-12-30  5:06 ` Profiling Kevin Greiner
2003-12-31  1:39   ` Profiling Lars Magne Ingebrigtsen
2004-01-04 15:37     ` Profiling Per Abrahamsen
2004-01-04 20:41       ` Profiling Lars Magne Ingebrigtsen
2003-12-31  1:49 ` Profiling Michael Cook
2004-01-03 16:56   ` Profiling Robert Marshall
2004-01-01 13:51 ` Spam processing slows down group exit (was: Profiling) Reiner Steib
2004-01-02 16:08   ` Spam processing slows down group exit Ted Zlatanov
2004-01-02 18:40     ` Reiner Steib [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=v9r7yikxc8.fsf@marauder.physik.uni-ulm.de \
    --to=4.uce.03.r.s@nurfuerspam.de \
    --cc=reiner.steib@gmx.de \
    /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).