Re: Idea for turbo expiry

[Lars Magne Ingebrigtsen <larsi@ifi.uio.no>]

Jason L Tibbitts III <tibbs@hpc.uh.edu> writes:

> I dipped into the expiry code to see why it was taking so much CPU every
> time I exited an nnml group.  It looks to me like it builds a list of all
> expirable articles and stats each of them in turn to see if they're old
> enough.

Yup.  The added complexity is there because you can gzip (etc) the
files, so nnml has to dance and jiggle around a bit to find the names
of the files.  

> My idea is to make the assumption that articles come in chronologically, so
> that if an article has a lower number, it it older.  Thus you can run the
> list of articles in numerical order and bail after you find one that is too
> young to expire. 

Or we could just assume that all the articles are in the .overview
file and use that to find out what articles are in the group.  That
should be much quicker, and only slightly less general.

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@ifi.uio.no * Lars Ingebrigtsen