info-gnus-english
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Slow header download on one group


From: Patrick May
Subject: Re: Slow header download on one group
Date: Tue, 20 Nov 2007 09:53:33 -0500
User-agent: Gnus/5.11 (Gnus v5.11) Emacs/22.1.50 (darwin)

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)


reply via email to

[Prev in Thread] Current Thread [Next in Thread]