Hi Mark, while I was trying to figure out and measure the performance
of a amavisd+postfix+spamassassin system, to see whether the
TimeElapsedSpamCheck was reliable, I was coming out with this patch
(see attach) to know which plugin is effectively loaded by amavisd. In
fact I haven't found such information in logs, and for testing purpose
one have to put at least in the same conditions as of the amavisd
user, and need to know all the plugins effectively loaded
(often the ones from the amavis user are not the same as the
system-wide SA). Can you include (or maybe a better one) it in the
next release?

Apart this I found that on a typical Dual Quad Xeon 5420 2.5Ghz
(indeed the extra 7 cores aren't used very much unless you increase
the concurrency level), a typical run with:

 "spamassassin -t -D < mailspam.msg"

takes around 10s, so the 7-8s shown for TimeElapsedSpamCheck by
amavisd-agent should be reliable, considering also that it should run
in daemon mode so the loading time shouldn't be counted.  Of these
10s, 7-8 seconds are usually taken by DNSBL SA checking; disabling all
the network checking (i.e. using spamassassin -t -D -L <
mailspam.msg), and redoing the tests, this 10s usually drops around
3.9s, while further using the compile (Rule2XS) feature, these 3.9s
drops to 2.6s (40% better). Now I'd like to do the same evaluation for
amavisd, i.e. with all the network testing disabled. Is there a way to
disable for instance the DNSBL and all the remote testing in one shot
from within amavisd.conf (more or less like the -L option does for the
spamassassin standalone command)? I tried to add sort of
"skip_rbl_checks 1" to user_prefs but isn't effective. In this way
should be possible to evaluate the theoretical peak limit (in
msgs/day) that a server could sustain per CPU/core and tune up the
performance accordingly under the best conditions. BTW, what other
values people reach under latest spamassassin (3.2.5) and amavisd-new
(2.6.1) in these subject?

At this point I would like to ask you whether the following feature
could be added and if it's worthwhile: it seems that most of the spam
is sent during night and the weekend. Would be possible to add
amavisd-new a feature to have it's behaviour selective according to
the time: e.g. since 75% of SA time is spent over DNS|RBL checks, and
often a server need to be much more responsive in sending and
receiving mails during daylight, would be fine to have a sort of two
profiles in amavisd-new: one for day (with maybe all network tests
disabled) and one for night and weekends under which the network
testing are disabled. In this way, when during daylight much server
power and responsiveness is needed for delivering mails it won't spent
much time in DNS|RBLs (ok, it will pass more spam), while during night
it could use all the tests available.

Such approach theoretically could be made with some sed|perl "search &
replace" scripts for user_prefs, commenting or uncommenting on the fly
some test, and then restarts the amavisd process, but this sound a
sort of ugly and awkward, and would be much more elegant inside amavisd.

Thanks
Bye
Giuseppe.


------------------------------------------------------------------------------
_______________________________________________
AMaViS-user mailing list
AMaViS-user@lists.sourceforge.net 
https://lists.sourceforge.net/lists/listinfo/amavis-user 
 AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3 
 AMaViS-HowTos:http://www.amavis.org/howto/ 

Reply via email to