Re: Not running expiry when I exit a group

[Jan Vroonhof <vroonhof@math.ethz.ch>]

Hrvoje Niksic <hniksic@srce.hr> writes:

> > I think that the only reason that total-expire needs to loop that way
> > is because the articles are not already marked as expirable.  The loop
> > is simply to determine which articles are expirable.
> 
> Yes, but this thread started with an assertion (hopefully true) that
> even in Elisp a thousand or so iterations shouldn't take too long.

It depends on what is iterated, which again depends on the back end.
For me (using nnfolder:xemacs-beta ) the slowness comes from the way
article seeking is implemented. As I posted before it does the
equivalent of

(setq bufje <xemacs-beta buffer>)
(progn
   (setq i 3000)
   (save-excursion
     (set-buffer bufje)
     (while (< 0 i)
       (setq i (+ i -1))
       (goto-char (point-min))
       (search-forward "X-Gnus-Article-Number: 3451"))))

3000 * searching 1.5MB is slow... There is no optimization for the
fact that the messages are consecutive.


It should just check all messages one for one (maybe stopping if it
found one that is too new) and intersect the result with the set of
non-read messages.

Jan