optimizing overview expiry (or: overview without expiry)

[Katsuhiro Kondou]

In article <20020203115318.W26676 at sunbeam.de.gnumonks.org>,
	Harald Welte <laforge at gnumonks.org> wrote;

}    for storagetoken -> overviewblock lookup, since it's usually needed the
}    other way around.  Without this index there would be no big improvement
}    over the current situation. 
     
Yes, it's true.

} b) Include a pointer to the overview information 'ovtoken' into 
}    CNFSARTICLEHEADER.  This way, at the time cnfs overwrites an article,
}    it could directly call into the overview code and tell it to remove
}    information about this article.

You mean CNFSARTHEADER will be variable length, since
I think the token needs to include all crossposted
newsgroups?  And innd needs to read the header before
writing new article.  I'm not sure how the perfomance
gets down here.

}   member, and call into the overview code, which removes overview info for
}   this article

I think it's necessary to consider how overview data
will be removed at the same time.  Just marked as
expired in index?  Or really delete the data?  The
former should be fast, but you still need to purge
old data by expireover.  The latter, I believe, it'll
be much slower to receiving ariticle.

} I'd like to receive your comments on this.  Has this been proposed before?

I thought many cases when I wrote the code.  But still
not get reached confortable place for all.

} What do you expect with regard to performance?  Would people be interested
} if I'd implement this?

It's interesting, but how do you think of storage methods
other than cnfs?
-- 
Katsuhiro Kondou