Re: nnimap slow on big groups

[Nuutti Kotivuori <naked@iki.fi>]

Kevin Greiner wrote:
> Nuutti Kotivuori <naked@iki.fi> writes:
>> 'nnimap' seems to be rather slow when selecting a large group - in
>> this case, around 65000 messages.
>>
>> A trivial poking around from me showed that it requests the entire
>> SEEN list from the group upon entry, while showing the "Updating
>> info for ..." message. Probably there are other operations that are
>> happening as well.
>>
>> Is there anything that can be done to alleviate the problem?
>
> 1) Agentize the server so that the 65K headers can be cached locally.
> 2) Set the agent-predicate to false so that the articles will not be
> stored locally.

I will try this later on when I get around to it, but I am pretty sure
it will not solve my problem.

The problem is not that 65k headers would have to be sent over the
network. I wouldn't even want to have them locally if I can avoid it.

The problem is that nnimap checks if the read article ranges
correspond to the 'seen' list on the server, and so fetches only the
article numbers of 65k seen articles - but even that is excessive.

-- Naked