Anne Ramey wrote:
Loren Wilton wrote:
Basically only two possibilities: you're thrashing the poor box to
death by
running out of memory, or network tests are taking an age. Or maybe
both.
ok, I had a pyzor test timing out, but I've removed that, and it's still
taking 6-15 seconds for the SA check.
I'm quite sure it's not the fault of the network tests, or at least not
only that. Here are the results from time spamassassin on the same
message (all 4 times):
without network checks:
real 0m5.968s
user 0m1.400s
sys 0m0.170s
real 0m32.084s
user 0m1.431s
sys 0m0.183s
Whith network checks:
real 0m11.509s
user 0m1.481s
sys 0m0.214s
real 0m21.296s
user 0m1.527s
sys 0m0.201s
How many children?
I've tried 8, 10, and 12 children with no noticable difference.
What load average?
load stays around 10
How much memory on the machine? How
much free memory?
my memory looks like this:
# free -m
total used free shared buffers cached
Mem: 2007 1807 200 0 23 292
-/+ buffers/cache: 1491 516
Swap: 2000 17 1982
`
Do you have a local caching DNS for the various RBL
checks?
not yet, the DNS server is just one hop.
Anne
Loren
