Gnus development mailing list
 help / color / mirror / Atom feed
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 14:30:45 +1100	[thread overview]
Message-ID: <87k2zx11cq.fsf@building.gnus.org> (raw)
In-Reply-To: <ufapp9v3ebj.fsf@epithumia.math.uh.edu> (Jason L. Tibbitts, III's message of "Fri, 30 Jan 2015 19:54:08 -0600")

Jason L Tibbitts III <tibbs@math.uh.edu> writes:

> debug-on-quit tells me it's sitting around in
> gnus-summary-expire-articles().  It's not doing anything with the IMAP
> server and the CPU is pegged.  Any idea how I can debug this, or get
> things back to a usable state?  (I guess I can always rename the
> folder.)  I once knew how to debug elisp but that's long been forgotten.

Hm...  let's see...  Is the nnimap group marked as a total-expirable
group?  Because then that function will go through all read articles in
the group and see whether it's eligible for expiration.

-- 
(domestic pets only, the antidote for overdose, milk.)
  bloggy blog http://lars.ingebrigtsen.no/



  reply	other threads:[~2015-02-05  3:30 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 [this message]
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
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=87k2zx11cq.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).