From: Lars Ingebrigtsen <larsi@gnus.org>
To: Jason L Tibbitts III <tibbs@math.uh.edu>
Cc: ding@gnus.org
Subject: Re: Gnus gets terribly slow when exiting high-traffic groups
Date: Thu, 05 Feb 2015 15:51:28 +1100 [thread overview]
Message-ID: <877fvxyn8v.fsf@building.gnus.org> (raw)
In-Reply-To: <ufar3u5vw76.fsf@epithumia.math.uh.edu> (Jason L. Tibbitts, III's message of "Wed, 04 Feb 2015 22:06:21 -0600")
Jason L Tibbitts III <tibbs@math.uh.edu> writes:
> Just pulled the last three commits from git and rebuilt. Entered and
> exited the group a couple of times to make sure that it hadn't magically
> gotten faster. (It hadn't.) G E shows:
>
> ("system-updates-2" 3
> ((1 . 139843))
> ((unexist
> (1 . 139804))
> (seen
> (136648 . 139843)))
> nil
> ((modseq)
> (uidvalidity . "1205769859")
> (active 1 . 139843)
> (permanent-flags %Answered %Flagged %Draft %Deleted %Seen %*)
> total-expire
> (expiry-wait . 2)))
>
> Doesn't look particularly problematic to me.
No, that looks the way it should.
I've tried reproducing this, but setting this up as a test case is quite
tricky.
Could you `M-x edebug-defun' though gnus-summary-expire-articles in
gnus-sum.el and see why it's looping there so much?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog http://lars.ingebrigtsen.no/
next prev parent reply other threads:[~2015-02-05 4:51 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 [this message]
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
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=877fvxyn8v.fsf@building.gnus.org \
--to=larsi@gnus.org \
--cc=ding@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).