From: Jason L Tibbitts III <tibbs@math.uh.edu>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: ding@gnus.org
Subject: Re: Gnus gets terribly slow when exiting high-traffic groups
Date: Thu, 05 Feb 2015 00:39:29 -0600 [thread overview]
Message-ID: <ufaa90s7tge.fsf@epithumia.math.uh.edu> (raw)
In-Reply-To: <871tm4zxjg.fsf@building.gnus.org> (Lars Ingebrigtsen's message of "Thu, 05 Feb 2015 17:23:47 +1100")
>>>>> "LI" == Lars Ingebrigtsen <larsi@gnus.org> writes:
LI> Try `M-x list-load-path-shadows' to list shadowing, or `M-x
LI> find-library RET gnus-sum RET' to see which version of gnus-sum
LI> you're loading.
Everything looks good there; my local copy of gnus seems to completely
shadow the system one (which is whatever comes with emacs 24.4.1). And
somehow, in the meantime, exiting that group has become instantaneous.
I don't get it. I still have another group that is slow, however:
("linux-wireless" 3
((1 . 118651))
((unexist)
(seen 86377
(111823 . 118651)))
nil
((modseq)
(uidvalidity . "1180109607")
(active 1 . 118651)
(permanent-flags %Answered %Flagged %Draft %Deleted %Seen NonJunk %*)
total-expire
(expiry-wait . 2)))
There are no unexpired articles at all in that group; entering it simply
exits back to the group buffer after a long pause at "Expiring
articles...". Stepping through gnus-summary-expire-articles shows it
iterating from 1 to, well, I assume 111822 but I didn't stick around to
find out.
- J<
next prev parent reply other threads:[~2015-02-05 6:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-31 1:54 Jason L Tibbitts III
2015-02-05 3:30 ` Lars Ingebrigtsen
2015-02-05 3:38 ` Jason L Tibbitts III
2015-02-05 3:47 ` Lars Ingebrigtsen
2015-02-05 4:06 ` Jason L Tibbitts III
2015-02-05 4:51 ` Lars Ingebrigtsen
2015-02-05 6:12 ` Jason L Tibbitts III
2015-02-05 6:18 ` Jason L Tibbitts III
2015-02-05 6:23 ` Lars Ingebrigtsen
2015-02-05 6:39 ` Jason L Tibbitts III [this message]
2015-02-06 0:42 ` Lars Ingebrigtsen
2015-02-06 0:47 ` 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=ufaa90s7tge.fsf@epithumia.math.uh.edu \
--to=tibbs@math.uh.edu \
--cc=ding@gnus.org \
--cc=larsi@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).