From: Patrick May <pjm@spe.com>
To: info-gnus-english@gnu.org
Subject: Slow header download on one group
Date: Mon, 19 Nov 2007 10:17:17 -0500 [thread overview]
Message-ID: <m2bq9qe03m.fsf@spe.com> (raw)
I see especially slow header downloads when accessing one
particular newsgroup. Even if that group shows only a dozen unread
posts, it loads much more slowly than a groups with over a hundred.
elp shows the following for the fast groups:
Function Name Call Count Elapsed Time Average Time
============================================================================ ========== ============ ============
gnus-retrieve-headers 3 5.690393 1.8967976666
gnus-group-read-group 1 3.42949 3.42949
gnus-summary-read-group 1 3.429393 3.429393
gnus-summary-read-group-1 1 3.429363 3.429363
gnus-select-newsgroup 1 2.889938 2.889938
gnus-fetch-headers 1 2.650536 2.650536
gnus-cache-retrieve-headers 1 2.638718 2.638718
gnus-agent-retrieve-headers 1 2.637814 2.637814
The slow group shows:
Function Name Call Count Elapsed Time Average Time
====================================================== ========== ============ ============
gnus-retrieve-headers 3 78.807254 26.269084666
gnus-group-read-group 1 47.025916 47.025916
gnus-summary-read-group 1 47.02571 47.02571
gnus-summary-read-group-1 1 47.025689 47.025689
gnus-select-newsgroup 1 42.567341 42.567341
gnus-fetch-headers 1 40.455486 40.455486
gnus-cache-retrieve-headers 1 39.304998 39.304998
gnus-agent-retrieve-headers 1 39.304134 39.304134
Could fragmentation in .newsrc.eld be the source of the problem?
Thanks,
Patrick
------------------------------------------------------------------------
S P Engineering, Inc. | Large scale, mission-critical, distributed OO
| systems design and implementation.
pjm@spe.com | (C++, Java, Common Lisp, Jini, middleware, SOA)
next reply other threads:[~2007-11-19 15:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-19 15:17 Patrick May [this message]
2007-11-20 0:50 ` Katsumi Yamaoka
2007-11-20 14:53 ` Patrick May
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=m2bq9qe03m.fsf@spe.com \
--to=pjm@spe.com \
--cc=info-gnus-english@gnu.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).