Re: ELP results for entering the Gnus list (~10 seconds elapsed time :)

[Lars Magne Ingebrigtsen <larsi@gnus.org>]

ShengHuo ZHU <zsh@cs.rochester.edu> writes:

>> It had one new message, together with the 36 ticked articles, some three
>> years old.
>>
>> ] wc ~/Mail/xemacs.gnus/.overview
>>   11308  324899 4232310 /home/daniel/Mail/xemacs.gnus/.overview
>> ] wc ~/Mail/xemacs.gnus/.marks
>>       1     130     776 /home/daniel/Mail/xemacs.gnus/.marks

[...]

>> gnus-get-newsgroup-headers-xover                        1           7.906612      7.906612
>> gnus-retrieve-headers                                   2           1.459674      0.7298370000
>
> Maybe gnus-nov-parse-line is the culprit, but it is an inline call in
> gnus-get-newsgroup-headers-xover.  So, could you evaluate
> gnus-get-newsgroup-headers-xover, then run elp again?

I think the explanation for this could be that if we call
`nnml-retrieve-headers' with article lists like '(45 73 20034)', then
that function will return a buffer with all the NOV headers between 45
and 20034.

*looks at code*

Yup, `nnheader-nov-delete-outside-range' is called to remove lines
that are before the smallest number and higher than the largest
number.  This means that `gnus-get-newsgroup-headers-xover' is parsing
a very large buffer.

I think we need to write a new function that looks at the "gaps" in
the article numbers and decides whether to remove the superfluous
lines or not according to some heuristic.  Say -- if the "gap" is more
than 50 articles, it will probably be more efficient to remove the
lines in between.

-- 
(domestic pets only, the antidote for overdose, milk.)
   larsi@gnus.org * Lars Magne Ingebrigtsen