-------- Original-Nachricht -------- > Datum: Fri, 31 Aug 2007 10:35:50 -0700 > Von: Tom Bombadil <[EMAIL PROTECTED]> > An: Tony Earnshaw <[EMAIL PROTECTED]> > CC: [email protected] > Betreff: Re: [dspam-users] avoid writing dspam_signature_data table
> > > Start over and this time use a group. From a 1500 user base with a 16GB > > MySQL InnoDB DB, using a shared group brought the DB back to 104MB, > > while the total accuracy after 135000 ham/spam is still 99+%. > > > > --Tonni > > > Thanks Tony. > > We already use shared group. Our problem is not the tokens table, but > the signatures table. > > BTW... another benefit of doing what I was thinking is that I could run > a read-only slave sql server on inbound mail, and the number of writes > would be close to zero. > Have you looked into the MySQLWrite* configuration part of dspam.conf? Could that help you to do what you wanted to do? > Cheers // Steve -- Ist Ihr Browser Vista-kompatibel? Jetzt die neuesten Browser-Versionen downloaden: http://www.gmx.net/de/go/browser
