Re: Idea for turbo expiry

[David Moore <dmoore@UCSD.EDU>]

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.

	Yeah, it does this if you use total-expire.

> 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.  I figure (judging from how much mail I save in some of my
> active folders) that this would cut my expiry time by a factor of 100 or
> more.

	I was thinking a good thing to do would be to get a list of all
of the files in the directory and intersect that list with the read
list, and only remove things in the intersection.  This wins big over
both the default and the start at low numbers approaches when the total
number of articles in the group is in the 10 thousands and you've only
got say 100 messages actually sitting there.

	But in any case the method used for total-expire can be improved
upon.

-- 
David Moore <dmoore@ucsd.edu>       | Computer Systems Lab      __o
UCSD Dept. Computer Science - 0114  | Work: (619) 534-8604    _ \<,_
La Jolla, CA 92093-0114             | Fax:  (619) 534-1445   (_)/ (_)
<URL:http://oj.egbt.org/dmoore/>    |