Gnus development mailing list
 help / color / mirror / Atom feed
From: Jason L Tibbitts III <tibbs@math.uh.edu>
To: ding@gnus.org
Subject: Debugging extremely long IMAP folder exit times
Date: Thu, 18 Jul 2019 13:34:12 -0500	[thread overview]
Message-ID: <ufa1rynb3a3.fsf@epithumia.math.uh.edu> (raw)

Occasionally a folder on an IMAP server will get into a state where it
takes ages for gnus to leave it.  I have one folder which before today
was quick to exit, but today suddenly takes over two minutes.  Gnus
shows "Expiring articles..." in the minibuffer.

If I C-u RET to enter the group, gnus thinks there are over 364000
messages in the group.  There are actually only about 9000 messages
there, according to another IMAP client.  My guess is that gnus is just
iterating over 364k entries to see what it should expire.

Note that when I run gnus-group-expire-articles on the group from the
summary buffer, it doesn't take very long at all.

Here is what's in newsrc.eld for the group.  I was worried there would
be a huge set of ranges in there but the data is quite simple.

("fail2ban" 3 ((1 . 364570)) ((unexist) (seen (364431 . 364570))) nil
((modseq) (uidvalidity . "1535374911") (active 1 . 364570)
(permanent-flags %Answered %Flagged %Draft %Deleted %Seen %*)
total-expire (expiry-wait . 7)))

Any hints on understanding what gnus is doing here, or suggestions on
how to speed it up?  I used to know quite a bit about Emacs and Gnus
internals but it has been many years now since I tried to do anything
interesting.

I am running emacs 26.2; gnus-version says "Gnus v5.13".

Thanks,

 - J<



             reply	other threads:[~2019-07-18 18:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-18 18:34 Jason L Tibbitts III [this message]
2019-07-18 20:31 ` Andreas Schwab
2019-07-18 22:15   ` Jason L Tibbitts III
2019-07-22 17:08     ` Jason L Tibbitts III
2019-07-22 17:54       ` Eric Abrahamsen
2019-07-22 18:44         ` Jason L Tibbitts III
2019-07-22 23:25           ` Eric Abrahamsen
2019-07-24 23:54             ` Jason L Tibbitts III
2019-07-25 20:09               ` Dan Christensen
2019-07-25 20:27                 ` Jason L Tibbitts III

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=ufa1rynb3a3.fsf@epithumia.math.uh.edu \
    --to=tibbs@math.uh.edu \
    --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).