email builder wrote: >>- - added PostgreSQL, MySQL 4.1+, and local SDBM file Bayes storage >>modules. SQL >> storage is now recommended for Bayes, instead of DB_File. NDBM_File >>support >> has been dropped due to a major bug in that module. >> >> > >What's the difference between the MySQL support that already existed in prior >versions? Is there anything those of us who already have our bayes data in >MySQL should do differently as of 3.1.0? > > >
The previous SQL support (Mail::SpamAssassin::BayesStore::SQL) was very generic, usable by multiple database drivers. With 3.1.0 we broke out the support and now include 2 very specific SQL backends (MySQL 4.1+ and PostgreSQL) in addition to the more generic backend. These specific backends make use of non-standard SQL features to get a speed boost. That said, if you were previously using SQL support with a MySQL database then you should be able to simply switch to using Mail::SpamAssassin::BayesStore::MySQL and get an instant speedup, assuming you already have MySQL 4.1+ installed. We do suggest that you switch your tables to InnoDB type tables (not currently the default) to get better data integrity (with the support of transactions). If you were using PostgreSQL with the previous support, you should switch (we're talking about a 7x - 27x improvement) ASAP, which might involve a complete wipe and rebuild of your database. Although, I would try an sa-learn --backup and sa-learn --restore before I completely gave up on the data. If you are interested in how well the various backends perform, compared to the others, see http://wiki.apache.org/spamassassin/BayesBenchmarkResults It is very hard to compare to previous versions, due to changes in other factors such as rules and message parsing code, but the improvments in 3.1 represent anywhere from a 2x - 27x improvements in previous performance. Hmmm....maybe some of the above should be captured in the documentation, patches welcome. Michael
signature.asc
Description: OpenPGP digital signature
