Re: Slow Access from Gnus

[Jake Colman <colman@ppllc.com>]

>>>>> "RS" == Reiner Steib <reinersteib+gmane@imap.cc> writes:

   RS> On Fri, Apr 04 2008, Jake Colman wrote:
   >>>>>>> "SB" == Steinar Bang <sb@dod.no> writes:
   SB> Have you tried sniffing the group opening with eg. wireshark to
   SB> see if the delay is simply network related?
   >> 
   >> When I enter a traditional nntp-based newsgroup (e.g., comp.emacs.help)
   >> I see some quick 'nntp read' messages and then I'm in.  Depending on the
   >> number of messages that have been posted since the last time I entered
   >> the newsgroup, I will see more or less 'nntp read' messages.
   >> 
   >> But when I entered gmane.discuss just now, with only two messages posted
   >> since I last checked it yesterday, I still saw a huge amount of 'nntp
   >> read' traffic.  It's almost as if Gnus is downloading the entire group
   >> and doesn't know how much I've already seen.

   RS> Set nntp-record-commands to t and check if the commands in the
   RS> *nntp-log* buffer are significantly different e.g. for
   RS> gnu.emacs.help and gmane.emacs.help.

Very, very odd.  The commands are identical.

For example:

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.
Even if I do a catch-up in my gmane group it rereads everything.  If I
enter comp.emacs twice in a row, the second is almost instantaneous.
Entering the same gmane group twice will take the same amount of time
each time as it does all those kilobytes of nntp reads.

-- 
Jake Colman
Director of Software Development
Principia Partners LLC
101 West Elm Street
Suite 620
Conshohocken, PA  19428
+1 (610) 755-9786
www.principiapartners.com