Gnus development mailing list
 help / color / mirror / Atom feed
From: Simon Josefsson <jas@extundo.com>
Cc: ding@gnus.org
Subject: Re: mail expiry has gotten very slow recently
Date: Tue, 18 Jun 2002 19:10:27 +0200	[thread overview]
Message-ID: <ilu4rg0bji4.fsf@latte.josefsson.org> (raw)
In-Reply-To: <vxkr8j4plr9.fsf@cinnamon.vanillaknot.com> (Karl Kleinpaste's message of "Tue, 18 Jun 2002 12:58:02 -0400")

Karl Kleinpaste <karl@charcoal.com> writes:

> I'm trying to understand why recent ("`cvs update' in the last couple
> weeks") Oort is having such trouble getting out of mail groups.  For
> one thing, it appears to be doing the job of expiry twice.  Here's a
> set of messages that came out of exiting a group with 1
> ready-to-be-expired article:
>
> No more unread articles (exiting)...
> Expiring articles...
> Deleting article 17408 in tomb
> Expiring articles in tomb
> Expiry...done
> Expiring articles...done
> No more unread newsgroups
> Returning to the group buffer
> Expiring articles...
> Expiring articles in tomb
> Expiry...done
> Expiring articles...done
>
> Can anyone discuss what's been done to expiry lately?  I'm watching
> XEmacs sit for as long as 5 seconds, seeming to do nothing, while
> expiry-related messages sit in the minibuf.

Expiring is done both in the Agent and in the backend now.  The agent
expiring isn't really efficient, but I hoped it wouldn't be too
noticable.  Splitting up gnus-agent-expire into smaller parts and
improving its efficiency would be good.

OTOH perhaps agent expiring simply shouldn't be performed when normal
expiring is performed?




  reply	other threads:[~2002-06-18 17:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-18 16:58 Karl Kleinpaste
2002-06-18 17:10 ` Simon Josefsson [this message]
2002-06-18 20:26   ` Karl Kleinpaste
2002-06-18 20:36     ` Simon Josefsson
2002-06-18 20:56       ` Karl Kleinpaste
2002-06-18 21:29         ` Simon Josefsson

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=ilu4rg0bji4.fsf@latte.josefsson.org \
    --to=jas@extundo.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).