On Tue, May 28, 2002 at 08:20:09PM -0700, Harry Putnam wrote: | In my tests, I've thrown 80-90 pieces of mail at spam assassin running | in the stock .procmailrc recipe with an added debug -D: | I see the cpu usage do a slow climb to around 50% (on an amd 400mhz) | Most of the time is spent in ranges below 25% though. And it takes | quite a while to process those 85 messages. | | real 2m41.954s | user 2m13.440s | sys 0m10.620s
| SA is doing quite a lot of processing... so maybe its normal?
It is normal for the way you're running SA. The way you're using it
(by running 'spamassassin'), for each message :
o start a perl process (not cheap)
o compile lots and lots of regexes (takes lots and lots of CPU)
o do the regex matches
o a bit of I/O too
If you use the spamc/spamd combo instead, you perform the first 2
steps only once. Then for each message you are starting just a spamc
process (much lighter weight than perl) and using the regexes that are
already compiled and in memory. The resources needed for this setup
is much lower than for running 'spamassassin' directly. (the setup is
also trivial to manage -- just run 'spamd' first (or
/etc/init.d/spamassassin if you use debian) and then run 'spamc' in
place of 'spamassassin')
HTH,
-D
--
the nice thing about windoze is - it does not just crash,
it displays a dialog box and lets you press 'ok' first.
GnuPG key : http://dman.ddts.net/~dman/public_key.gpg
msg05544/pgp00000.pgp
Description: PGP signature
