SpamAssassin version 3.2.5, running on Perl version 5.8.8, Solaris 9
Using MySQL for Bayes database.

I'm wondering if our Bayes token database is too big, and why.

Based on some posts to this list, I decided to try converting our Bayes and AWL 
databases to InnoDB to improve performance.  So I copied the database to a 
non-production MySQL server and tried to convert it there.  It has taken 4 days 
to convert!  I'm thinking something must be wrong.

Here is the output I'm getting from our Bayes expire job:

Tue Sep 30 00:12:00 EDT 2008 Forcing Bayes expiry run
expired old bayes database entries in 193 seconds
104999743 entries kept, 147355 deleted
token frequency: 1-occurrence tokens: 0.12%
token frequency: less than 8 occurrences: 0.05%
Tue Sep 30 00:15:28 EDT 2008 Done

Wed Oct 1 00:12:00 EDT 2008 Forcing Bayes expiry run
expired old bayes database entries in 210 seconds
105000814 entries kept, 242825 deleted
token frequency: 1-occurrence tokens: 0.11%
token frequency: less than 8 occurrences: 0.06%
Wed Oct 1 00:15:47 EDT 2008 Done

Thu Oct 2 00:12:00 EDT 2008 Forcing Bayes expiry run
expired old bayes database entries in 206 seconds
105032264 entries kept, 239214 deleted
token frequency: 1-occurrence tokens: 0.13%
token frequency: less than 8 occurrences: 0.06%
Thu Oct 2 00:15:39 EDT 2008 Done

And here is the information from the local.cf file:

bayes_expiry_max_db_size  500000

So the config file says 500 thousand tokens, but the database has 105 million 
entries.  Have I misunderstood something, or is expiry not working correctly?


Reply via email to