[Mimedefang] BIG problems with mimedefang

[Matthew.van.Eerde at hbinc.com]

David F. Skoll wrote:
> Matthew.van.Eerde at hbinc.com wrote:
> 
>> Once you get beyond a certain traffic level the BerkeleyDB
>> implementation of the Bayes database becomes a bottleneck and you
>> need to move to a SQL-daemon database.
> 
> If that's the case, SpamAssassin has a seriously broken BerkeleyDB
> Bayes implementation.

You say to-MAY-to, I say to-MAH-to...

> Even SpamAssassin shouldn't require locking unless the Berkeley DB
> file is being written to.  If it's only being read, then concurrent
> access shouldn't be a problem.

Most bayesian analyses result in a write to add the new tokens and update the token counts.

Every so often a bayesian analysis results in a HUGE write to expire old tokens.

Any mail that comes along during an expiry is going to have to sit and wait... the slaves pile up, processes drop into swap, and it's La Brea all over again.

-- 
Matthew.van.Eerde (at) hbinc.com               805.964.4554 x902
Hispanic Business Inc./HireDiversity.com       Software Engineer