From: "Jason L Tibbitts III" <tibbs@math.uh.edu>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: ding@gnus.org
Subject: Re: Long wait for "Expiring Articles..."
Date: Tue, 04 Feb 2014 18:05:25 -0600 [thread overview]
Message-ID: <ufabnymqv96.fsf@epithumia.math.uh.edu> (raw)
In-Reply-To: <ufa38jzssz8.fsf@epithumia.math.uh.edu> (Jason L. Tibbitts, III's message of "Mon, 03 Feb 2014 16:59:23 -0600")
Decided to check how to profile elisp and instrumented the gnus package,
but the results don't seem particularly useful. Here's the top ten functions:
The only function called more than a few times was gnus-remove-if at 307
times, but with a call time down in the noise.
gnus-summary-exit 1 45.138563005 45.138563005
gnus-run-hooks 8 45.091998884 5.6364998605
gnus-summary-expire-articles 1 45.0919888 45.0919888
gnus-list-of-read-articles 1 0.255410847 0.255410847
gnus-uncompress-range 1 0.213805775 0.213805775
gnus-score-save 1 0.043802103 0.043802103
gnus-list-range-difference 2 0.04156259 0.020781295
gnus-write-buffer 1 0.040823595 0.040823595
gnus-request-expire-articles 1 0.017794266 0.017794266
gnus-prin1 1 0.002680406 0.002680406
Digging into my .gnus, I found this:
;(remove-hook 'gnus-summary-prepare-exit-hook 'gnus-summary-expire-articles)
Now, my .gnus really does date back from before the time Larsi started
working on it, so any memories of why I would have previously tried to
keep that function from being called are long gone. But I eval'ed that
piece of code and group exiting is fast now.
So, what am I missing by doing this? Is there a better way to handle
expiring read articles from my mail folders? Or is there more I can do
to debug just why this is taking so long? I used to actually know how
to do things in emacs but that, too, has been long forgotten.
- J<
next prev parent reply other threads:[~2014-02-05 0:05 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
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 [this message]
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=ufabnymqv96.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).