From: "Bjørn Mork" <bjorn@mork.no>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: "Jason L Tibbitts III" <tibbs@math.uh.edu>, ding@gnus.org
Subject: Re: Long wait for "Expiring Articles..."
Date: Mon, 03 Feb 2014 23:12:18 +0100 [thread overview]
Message-ID: <87sirzq20t.fsf@nemi.mork.no> (raw)
In-Reply-To: <87zjm73ljq.fsf@building.gnus.org> (Lars Ingebrigtsen's message of "Mon, 03 Feb 2014 13:59:05 -0800")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> "Jason L Tibbitts III" <tibbs@math.uh.edu> writes:
>
>> Lately I've noticed the time taken to exit a group, when gnus shows
>> "Expiring Articles..." has been pretty long. Even going into a group
>> with only a handful of articles, reading them and exiting can cause a
>> 30+ second wait. During this time, Emacs consumes 100% CPU while my
>> IMAP server is idle.
>
> `(setq nnimap-record-commands t)', and after you've seen this problem,
> go to the *imap log* buffer and see what's there. The commands are
> timestamped, so it should give us an idea just what command is taking so
> long.
Was this patch from John Magorrian ever merged?:
http://article.gmane.org/gmane.emacs.gnus.general/80546
I've been using it for the last few years, and it is pretty essential if
you ever do expiry in an IMAP folder with high UIDs.
Bjørn
next prev parent reply other threads:[~2014-02-03 22:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-03 7:14 Jason L Tibbitts III
2014-02-03 21:59 ` Lars Ingebrigtsen
2014-02-03 22:12 ` Bjørn Mork [this message]
2014-02-03 22:40 ` Lars Ingebrigtsen
2014-02-04 8:19 ` Bjørn Mork
2014-02-03 22:59 ` Jason L Tibbitts III
2014-02-05 0:05 ` Jason L Tibbitts III
2014-02-05 1:34 ` Jason L Tibbitts III
2014-02-05 1:36 ` Lars Ingebrigtsen
2014-02-06 2:17 ` Lars Ingebrigtsen
2014-02-06 4:32 ` Jason L Tibbitts III
2014-02-06 6:24 ` Jason L Tibbitts III
2014-02-06 6:39 ` Lars Ingebrigtsen
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=87sirzq20t.fsf@nemi.mork.no \
--to=bjorn@mork.no \
--cc=ding@gnus.org \
--cc=larsi@gnus.org \
--cc=tibbs@math.uh.edu \
/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).