We have local DNS servers and cache/have feeds to some of the blacklists
to help with the network testing processing.
This is what we have observed too. We have watched top for observing
memory use, CPU use (user versus idle versus wait), and slow network
tests will cause the spamd childs to keep busy but not be using as much
user CPU time. Other causes of wait cpu time are I/O related as well,
such as having a slow hard disk (perhaps being used for swap).
For example a recent Cpanel problem with spamd was it was continuosly
trying to do something with a users' file while it processed, this extra
I/O was slowing things down. (My advice in this message is not regarding
cpanel servers though)
Basically get enough ram to run as many processes as it takes to max out
the CPUs with almost all "user" processing.
An older server running with 2GB ram hadn't enough simultaneous spamd
processes to process the volume of messages that we need. If you can
have a motherboard that uses DDR2 memory, it is dirt cheap these days
to fill it with lots of ram.
We upped ram to 8GB so we can run more simultaneous spamd processes than
previous servers, and that's just about the right amount of ram
currently for the volume a quad-core AMD machine can process and fully
utilize the CPUs.
>
> - is spamd taking up the CPU time or is it your MTA queuing taking up
> CPU time? 3.2.3+ will wait longer for DNS responses, decreasing
> throughput per child but not increasing CPU time per message
>
> If you describe *how* you're using SA someone might have some more
> suggestions.
>
> Daryl
--
/*
Jason Philbrook | Midcoast Internet Solutions - Wireless and DSL
KB1IOJ | Broadband Internet Access, Dialup, and Hosting
http://f64.nu/ | for Midcoast Maine http://www.midcoast.com/
*/
