Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
Cc: Ding Mailing List <ding@gnus.org>
Subject: Re: No Gnus 0.3 slower than Oort Gnus 0.24 spam handling
Date: Tue, 21 Mar 2006 11:02:08 -0500	[thread overview]
Message-ID: <4nek0vdbwf.fsf__49420.1508154676$1142959235$gmane$org@asimov.bwh.harvard.edu> (raw)
In-Reply-To: <y201wx0lvd6.fsf@newsserver.nospam.net>

On 17 Mar 2006, alberto.l@nospam.net wrote:

> I recently upgraded from Oort 0.24 to No 0.30 and my spam handling has
> become quite slow.  Here is my situation:
>
> - I use nnfolder mail storage
> my spam handling configuration (using bogofilter):
> - splits spam into mail.spam.temp
> - on exiting, spam in all groups is moved to mail.spam.save
> - mail.spam.temp and mail.spam.save are spam groups
> - the spam process destination for mail.spam.save is nil
>
> When I enter mail.spam.temp to check for false spam positives, on
> quitting it all spam-marked messages are moved to mail.spam.save.
> This is quite slower with No 0.30 w.r.t. Oort 0.24 because,
> apparently, both mail.spam.temp and mail.spam.save are written to
> disk each time a single message is moved.  With Oort 0.24 as far as I
> can understand both groups are written to disk only once.

Alberto,

thank you for the comments.

Some people on the 'ding' mailing list (which is the main vehicle for
Gnus development) have commented that nnfolder is much slower with
CVS Emacs than with the older releases.  Could this be part of the
problem?

Also, is it possible for you to use the CVS version of Gnus, so we can
debug this problem against the latest version of spam.el?

Thanks again
Ted

  reply	other threads:[~2006-03-21 16:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-17 19:33 Alberto L
2006-03-21 16:02 ` Ted Zlatanov [this message]
     [not found] ` <4nek0vdbwf.fsf@asimov.bwh.harvard.edu>
2006-03-21 17:31   ` Alberto L
2006-03-22 15:22     ` Ted Zlatanov

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='4nek0vdbwf.fsf__49420.1508154676$1142959235$gmane$org@asimov.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).