From: Reiner Steib <reinersteib+gmane@imap.cc>
To: Jake Colman <colman@ppllc.com>
Cc: gmane-discuss@hawk.netfonds.no, ding@gnus.org
Subject: Re: Slow Access from Gnus
Date: Fri, 04 Apr 2008 19:56:57 +0200 [thread overview]
Message-ID: <v94pah4i6u.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <764pahfsdj.fsf@dev-d01.ppllc.com> (Jake Colman's message of "Fri, 04 Apr 2008 13:21:28 -0400")
On Fri, Apr 04 2008, Jake Colman wrote:
> 20080404T131502.278 news.gmane.org GROUP gmane.emacs.gnus.general
> 20080404T131502.400 news.gmane.org XOVER 1-66679
> 20080404T131611.177 free.teranews.com GROUP comp.emacs
> 20080404T131611.296 free.teranews.com XOVER 1-69787
>
> Yes, it appears that for every gmane group it actually rereads the
> entire "active file" (do I know what I'm talkig about?) or something.
Gnus fetches the whole NOV (overview) data if `gnus-fetch-old-headers'
is t. Try setting it to some number, say 100. Does it help?
Then you should see something like this in the *nntp-log* buffer:
[DATE...] news.gmane.org XOVER 66578-66679
(See the function `nntp-retrieve-headers-with-xover')
In contrast to "normal" news servers, Gmane doesn't expire articles so
the overview might become really large.
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
next prev parent reply other threads:[~2008-04-04 17:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <76abkahc6i.fsf@dev-d01.ppllc.com>
[not found] ` <87r6dmobkp.fsf@topper.koldfront.dk>
[not found] ` <76sky2fksc.fsf@dev-d01.ppllc.com>
[not found] ` <877ifdhip3.fsf@dod.no>
[not found] ` <76d4p5g22s.fsf@dev-d01.ppllc.com>
2008-04-04 15:19 ` Reiner Steib
2008-04-04 17:21 ` Jake Colman
2008-04-04 17:56 ` Reiner Steib [this message]
2008-04-04 19:18 ` Jake Colman
2008-04-04 19:54 ` Reiner Steib
2008-04-04 20:07 ` Sven Joachim
2008-05-24 13:09 ` Reiner Steib
2008-04-06 18:03 ` Jake Colman
2008-04-06 20:23 ` Reiner Steib
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=v94pah4i6u.fsf@marauder.physik.uni-ulm.de \
--to=reinersteib+gmane@imap.cc \
--cc=Reiner.Steib@gmx.de \
--cc=colman@ppllc.com \
--cc=ding@gnus.org \
--cc=gmane-discuss@hawk.netfonds.no \
/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).