Ramprasad wrote:
I can tell you right now, its either Net tests or poorly written
rules. Otherwise SA runs pretty darn good.
Darn good is how good ?
On a Dual Xeon with 4GB ram can SA scan 30k mails per hour.
Today at 15k the machine starts signalling problems , 20k is the max it
can do beyond which there are unacceptable delays
Spammassassin -D --lint < some_test_email
How do I know what percentage of time is taken by individual tests ?
Try installing mailwatch in a limited manner (mailwatch.sf.net, works
only with mailscanner), you do not have to use it for quarantine
management or any other thing.. under tools you have a link for a lint
test which gives you nicely formatted html page with the time taken for
each test.
As Chris mentioned.. network tests (especially razor/pyzor) could be
responsible for SA delay. If you have a lot of servers try running a
local only pyzord (see pyzor.sf.net).
- dhawal
Thanks
Ram
- Re: bottleneck analsyis on spamassassin Dhawal Doshy
-