sa-update and sa-compile

Holger Nöfer holger at noefer.org
Wed Jun 13 20:56:33 IST 2007


Richard Frovarp schrieb:
> Holger Nöfer wrote:
>> Hi,
>>
>> how do you use sa-update and sa-compile?
>>
>> If I use sa-update it puts the rules to
>> /var/lib/spamassassin/3.002000. If I use
>> sa-compile it compiles the rules to
>> /var/lib/spamassassin/compiled.
>>
>> Does sa-compile use the rules in /var/lib/spamassassin/3.002000
>> or in /usr/local/share/spamassassin?
>>
>> If I test spamassassin with
>> spamassassin -D --lint -p /etc/mail/spamassassin/mailscanner.cf
>> it seems that spamassassin uses the files under
>> /var/lib/spamassassin/3.002000 and /var/lib/spamassassin/compiled.
>> Is that right?
>> If yes, do you delete /var/lib/spamassassin/3.002000 to only use
>> the /var/lib/spamassassin/compiled files?
>> Without /var/lib/spamassassin/3.002000 files spamassassin is much
>> faster.
>>
>> Best regards,
>> Holger
>>   
> 
> It tries to use all the rules it can find. sa-compile only works on body
> rules, and it doesn't work for all of those rules. I've seen reports
> stating 60% of the body rules can be compiled. Furthermore, there isn't
> a guarantee that the compiled version of the rules are identical to the
> original version of the rules. Therefore, SA checks with the original
> rules for any that hit from the compiled list. So no, don't delete
> /var/lib/spamassassin/3.002000 as no rules there will be used. Deleting
> that directory probably means you're only using local rules in
> /etc/mail/spamassassin.

Hi,

I did some research today on my virtual private
server, before I change my big mail servers.
The VPS is not very fast and not much ram but for scanning
some mails it's ok.

I did some local test, without network tests (blacklists,
dcc and others).

The first I can say is that I agree with Richard, so don't delete
/var/lib/spamassassin/3.002000 ;-)

I did the test with 675 spam mails with different size.

only updates spamasassin rules
real    3m16.442s		576 spam mails detected
user    1m37.806s
sys     0m0.412s

real    3m18.819s		576 spam mails detected
user    1m38.896s
sys     0m0.482s


updates spamasassin rules + compiled
real    2m11.203s		576 spam mails detected
user    1m4.988s		~ 33% faster
sys     0m0.392s

real    2m13.268s		576 spam mails detected
user    1m5.735s		~ 33% faster
sys     0m0.404s


updates spamasassin rules + sare rules
real    6m35.319s		593 spam mails detected
user    3m16.920s		~ 200% slower
sys     0m0.548s

real    6m32.300s		593 spam mails detected
user    3m15.861s		~ 200% slower
sys     0m0.609s


updates spamasassin rules + sare rules + compiled
real    3m33.363s		593 spam mails detected
user    1m46.339s		~ 9% slower
sys     0m0.603s

real    3m31.846s		593 spam mails detected
user    1m45.265s		~ 9% slower
sys     0m0.516s


sare rules + compiled (bad idea, spamassassin
takes only /usr/local/share/spamassassin Rules,
so don't delete /var/lib/spamassassin/3.002000)
real    2m19.859s		573 spam mails detected
user    1m9.448s		~ 30 faster
sys     0m0.393s

real    2m20.007s		573 spam mails detected
user    1m9.553s		~ 30 faster
sys     0m0.391s


Perhaps these are some useful information.

Best regards,
Holger


More information about the MailScanner mailing list