In the past we have seen some slowness for bayes and AWL (mostly AWL). We found after a couple million rows in AWL that the system starts getting real slow. We setup a script to prune records that have a high bayes threshold but a count of 1 (usually anonymous spammers). They will not use that IP/sender combination again anyways. This keeps it nice and tidy.
As for the bayes, you might want to manually expire the old tokens. That might help. But this is just a guess at this time. What would be more useful are things like the number of records you have in the db, the hardware of the DB (memory, etc), and any other good information that might help make a better guess. Gary Wayne Smith > -----Original Message----- > From: David Morton [mailto:[EMAIL PROTECTED] > Sent: Thursday, August 10, 2006 2:28 PM > To: users@spamassassin.apache.org > Subject: slow sql bayes store > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Greetings... > > On the Maia Mailguard mailing list, we have encountered a number of folks > (myself included) that are seeing some slow performance in the bayes > storage > when using mysql (innodb engine), taking anywhere from .5 to 10 seconds to > store/update all the tokens for a message. Has anyone else seen this? > > > > - -- > David Morton > Maia Mailguard - http://www.maiamailguard.com > Morton Software Design and Consulting - http://www.dgrmm.net > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.2.2 (GNU/Linux) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iD8DBQFE26TLUy30ODPkzl0RAgNHAJ9UNgS4zudN5dAdkcOGw/ljmAe5tACgzzNQ > j0YStIUlkDn2qx9LXVZpUus= > =tvfh > -----END PGP SIGNATURE-----
