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 21:54:50 +0200 [thread overview]
Message-ID: <v9bq4p2y5x.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <76ve2xe8ep.fsf@dev-d01.ppllc.com> (Jake Colman's message of "Fri, 04 Apr 2008 15:18:06 -0400")
On Fri, Apr 04 2008, Jake Colman wrote:
> WOW! What a difference! My prior setting for
> 'gnus-fetch-old-headers' was t. I set it to 500 and I now enter the
> group virtually instantaneously. Is there any practical downside to
> specifying a number instead of 't'?
You might not see old posting in the threads...
,----[ (info "(gnus)Filling In Threads") ]
| `gnus-fetch-old-headers'
| If non-`nil', Gnus will attempt to build old threads by fetching
| more old headers--headers to articles marked as read. If you would
| like to display as few summary lines as possible, but still
| connect as many loose threads as possible, you should set this
| variable to `some' or a number. If you set it to a number, no
| more than that number of extra old headers will be fetched. In
| either case, fetching old headers only works if the back end you
| are using carries overview files--this would normally be `nntp',
| `nnspool', `nnml', and `nnmaildir'. Also remember that if the
| root of the thread has been expired by the server, there's not
| much Gnus can do about that.
|
| This variable can also be set to `invisible'. This won't have any
| visible effects, but is useful if you use the `A T' command a lot
| (*note Finding the Parent::).
`----
> What setting do _you_ use?
I've set it to t, but I fetch all newsgroups groups from my local
leafnode server, which does expire Gmane groups, so I don't experience
the slowness. Maybe we should warn about this setting when using
news.gmane.org. Do others see the slow access on Gmane with as well
with `gnus-fetch-old-headers' set to t?
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
next prev parent reply other threads:[~2008-04-04 19:54 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
2008-04-04 19:18 ` Jake Colman
2008-04-04 19:54 ` Reiner Steib [this message]
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=v9bq4p2y5x.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).