From: Patrick May <pjm@spe.com>
To: info-gnus-english@gnu.org
Subject: Re: Slow header download on one group
Date: Tue, 20 Nov 2007 09:53:33 -0500 [thread overview]
Message-ID: <m2oddpklxu.fsf@spe.com> (raw)
In-Reply-To: <b4my7ctrb8h.fsf@jpl.org>
Katsumi Yamaoka <yamaoka@jpl.org> writes:
>>>>>> Patrick May wrote:
>> 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.
[ . . . ]
>> Could fragmentation in .newsrc.eld be the source of the problem?
>
> I don't think so. Though I haven't tried supernews.com, I guess
> there might be a big gap between old article numbers and latest ones
> in the server. What does evaluating the following Lisp form return?
>
> (gnus-active "news.group.name")
(1122781 . 1963402)
> It says for my local news server as:
>
> (gnus-active "gnu.emacs.gnus")
> => (57391 . 59194)
>
> but for news.motzarella.org it says:
>
> (gnus-active "nntp+motzarella:gnu.emacs.gnus")
> => (156 . 30068314)
>
> In the later case, Gnus consumes memory wastefully and takes time
> while fetching headers even if there are no more than hundreds
> articles.
My difference is 840 thousand or so. Is that enough to be a
problem?
> For such cases Gnus offers a workaround. If it is just your case,
> try setting the `gnus-newsgroup-maximum-articles' variable to a
> certain number. For example:
>
> (setq gnus-newsgroup-maximum-articles 10000)
>
> It lets Gnus disregard old articles than the latest 10000 articles
> in all groups and work fast.
I'll give that a try. Thanks for the help!
Regards,
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)
prev parent reply other threads:[~2007-11-20 14:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-19 15:17 Patrick May
2007-11-20 0:50 ` Katsumi Yamaoka
2007-11-20 14:53 ` Patrick May [this message]
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=m2oddpklxu.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).