From: Simon Josefsson <jas@extundo.com>
Cc: ding@gnus.org
Subject: Re: expiry-target with nnimap destination slowdown
Date: Thu, 31 Jul 2003 03:14:15 +0200 [thread overview]
Message-ID: <ilu1xw71orc.fsf@latte.josefsson.org> (raw)
In-Reply-To: <vqowue8xrbc.fsf@astazou.imag.fr> (Nicolas Kowalski's message of "Thu, 24 Jul 2003 10:27:35 +0200")
Nicolas Kowalski <Nicolas.Kowalski@imag.fr> writes:
> Hello.
>
> I use nnimap as a secondary mail method. The nnimap:mail/* groups are
> expired in nnimap:old/* groups. One of this nnimap:old/* group is
> going huge (~5000 messages), so I now I can notice a serious slowdown
> when the expiration process runs.
>
> For example, I see in the *imap-log* buffer that the nnimap backend
> store "\\Seen" on all messages of the nnimap:old/verimag group, and
> this for each article expired in nnimap:mail/verimag.
>
> The imap-log corresponding to the expiration of /only/ one article can
> be downloaded here (~170k) :
>
> http://www-verimag.imag.fr/~kowalski/imap.log
>
> Any tips for speeding it up ?
The imap.log file doesn't seem to be available now, but maybe you
could rename the group old/foo to old/foo2 and create a new old/foo?
If this happens often, maybe using a old/foo-YYYY-MM or similar scheme
could help.
next prev parent reply other threads:[~2003-07-31 1:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-24 8:27 Nicolas Kowalski
2003-07-31 1:14 ` Simon Josefsson [this message]
2003-07-31 7:35 ` Nicolas Kowalski
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=ilu1xw71orc.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).