have you turned off RBLs and other network tests you dont need and disabled any non-standard rules and plugins?
if you are using RBLS's have a a caching nameserver on the SA machine itself (even if your 'local' DNS server is only a couple of milliseconds away a caching namesserver on the box itself helps hugely). any clues on the maillog or of you run spammassassin with "--lint --debug" on a sample? -- Martin Hepworth Oxford, UK On 17 November 2011 15:55, Tom <t...@t0mb.net> wrote: > Greetings, > > ======= Information ============== > Old Version: spamassassin-3.2.5-1.el5 > New EL5 Version: spamassassin-3.3.1-2.el6.x86_**64 > New EL6 Version: spamassassin-3.3.1-2.el5.x86_**64 > > SPAMDOPTIONS="-d -L -i 10.44.219.208 -A 10.44.217.0/20 -m 40 -q -x -u > spamd --min-children=40" > > Other info Bayes module disabled, compiled regexes being used, RBL checks > disabled, network checks disabled. > ============================= > > I have had a problem trying to upgrade from 3.2.5 to 3.3.1 on both > CentOS5, and a brand new install on CentOS6. > > I want to retain the basic configuration I'm using. Basically, 3.2.5 > works fine, and I'm processing up to 600 mails per minute sometimes. When > I try and use 3.3.1 with the same general configuration, mail seems to be > processed correctly, and the strength of the newer rules is brilliant in > terms of accuracy, but as soon as I start the service, the load average on > the server starts climbing until it roughly equals the number of children > we have configured, and performance starts to get pretty bad. This seems > to happen whether I use the round-robin method or the default scaling > method. > > I can't really see why my load average is climbing so high. > > Can anyone suggest what is happening and why it might be so different? > I've been banging my head against the desk trying to get to the bottom of > this. I first tried to upgrade to 3.3.1 a while ago, and got the issue. > This was with a src rpm build of the apache supplied tarball. Then centos > 5.7 came out, and they upgraded to 3.3.1, so I came in to work one day with > my whole cluster falling to pieces and after failing to fix the issue, I > downgraded again and excluded spamassassin from updates. I've now tried on > centos6, and it's still the same. > > Many thanks. Tom Boland. >
