Comments on Optimizing DSPAM + MySQL 4.1
DSPAM is a scalable and open-source content-based spam filter designed for multi-user enterprise systems. It's great at filtering out spam but on busy mailservers the pruning of the MySQL databases takes way too long time. This small tutorial/hack can speed up the pruning of old data considerably.
5 Comment(s)
Comments
Good Article, it holds its own. It has clear steps, explaining to the user what everything does and on top of that you give the reasons, why or why not a person should use this... good job, very easy read.
I've seen a lot of people write quick and dirty how-to faqs in the past that are similar to this minus one factor that makes this the best I've seen. I actually understand the purpose and content as a systems engineer without having to go learn mysql in depth to make this work. It's brief and very helpful in decided if this is right on a given system.
Thanks!
Very useful!
Did you tried to use postgresql? Seems, postgresql queries isn't optimal too ;-)
With dspam default install database schema with not all the corectly index ,my dspam database about 3G tale 1H30m to run the default maintenance script ,imagine my system complety frozen.
The minimum step is to do the correct dspam index like in this article .
Tks for your maintenance query .
Do you use MyISAM engine or InnoDB in your installation? Does it make any difference for index optimization?