From: Wolfgang Jenkner <wjenkner@inode.at>
To: Tassilo Horn <tassilo@member.fsf.org>
Cc: ding@gnus.org
Subject: Re: Excessive nntp reads since today
Date: Tue, 12 Jun 2012 16:35:38 +0200 [thread overview]
Message-ID: <85pq94k37p.fsf@iznogoud.viz> (raw)
In-Reply-To: <87y5nsbqj4.fsf@thinkpad.tsdh.de> (Tassilo Horn's message of "Tue, 12 Jun 2012 15:36:47 +0200")
On Tue, Jun 12 2012, Tassilo Horn wrote:
> Wolfgang Jenkner <wjenkner@inode.at> writes:
>
>>> My `gnus-fetch-old-headers' is 'some, so it might want to fetch some
>>> older messages to connect new articles in a thread, but not so many.
>>> I just entered the gmane xetex group which had 4 new articles. The
>>> summary showed those 4 articles + 2 old articles from yesterday (the
>>> 4 new were replies of the 2 old ones). But when entering the group,
>>> the "nntp read: <x> kb" message counted to more than 12.000.
>>>
>>> I suspect this change is the culprit, so I added Wolfgang to the Cc.
>>>
>>> ,----
>>> | commit 44f603535c63aab124e139b145fce20fff488f38
>>> | Author: Wolfgang Jenkner <wjenkner@inode.at>
>>> | Date: Mon Jun 11 23:49:17 2012 +0200
>>> |
>>> | Make `A T' work when agentized
>>> |
>>> | * gnus-agent.el (gnus-agent-retrieve-headers): Recalculate the range of
>>> | articles when fetch-old is non-nil (bug#11370).
>>> `----
>>
>> I admit that it hadn't occurred to me to test this patch with
>> non-default values of gnus-fetch-old-headers, but the docstring of this
>> variable actually seems to match the behaviour you describe...
>
> It matches the behavior in that it had to fetch 2 additional messages to
> fill in gaps in lose thread branches.
The docstring states that it fetches all old headers (though only some
subset of them is displayed).
> But the two old messages were from yesterday, and that's a low-traffic
> group with about 20 messages in the last week. There's no chance that
> this required fetching 12 MB of header data, right?
Perhaps tracing (or stepping through) gnus-agent-retrieve-headers could
give a clue?
Wolfgang
next prev parent reply other threads:[~2012-06-12 14:35 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-12 12:11 Tassilo Horn
2012-06-12 13:11 ` Wolfgang Jenkner
2012-06-12 13:36 ` Tassilo Horn
2012-06-12 14:35 ` Wolfgang Jenkner [this message]
2012-06-12 15:56 ` Wolfgang Jenkner
2012-06-12 16:31 ` Tassilo Horn
2012-06-13 13:48 ` Wolfgang Jenkner
2012-06-13 15:18 ` Tassilo Horn
2012-06-13 16:36 ` Wolfgang Jenkner
2012-06-13 18:57 ` Tassilo Horn
2012-06-16 11:37 ` Wolfgang Jenkner
2012-06-16 12:53 ` Tassilo Horn
2012-06-16 14:18 ` Wolfgang Jenkner
2012-09-05 13:56 ` Lars Ingebrigtsen
2012-09-05 14:38 ` Tassilo Horn
2012-09-05 16:19 ` Lars Ingebrigtsen
2012-09-05 17:16 ` Tassilo Horn
2012-09-05 17:34 ` Wolfgang Jenkner
2012-09-05 17:36 ` Tassilo Horn
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=85pq94k37p.fsf@iznogoud.viz \
--to=wjenkner@inode.at \
--cc=ding@gnus.org \
--cc=tassilo@member.fsf.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).