Re: Agent gone mad?

[Simon Josefsson <jas@extundo.com>]

Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:

> Simon,
>
> does this ring a bell with you?  Does the agent header caching stuff
> do more work for nnimap than for nntp groups?  Or is there additional
> header caching going on for nnimap?

Nnimap used to do its own NOV caching which was (usually) more
efficient than the Agent caching (specifically -- nnimap only retrieve
NOV headers in blocks, leaving no gaps in the .overview file, this
means it sometimes does too much work, but it can pay this back by
needing less round trips and probably loading the server less).  But
this is now probably disabled:

(defvoo nnimap-nov-is-evil gnus-agent

Although this should really be backend dependent, and only be disabled
on agentized backends.  I remember trying to optimize the nntp.el code
too, but the NNTP command trace doesn't display the received data so
it was a little difficult to debug.