MailScanner/Spamassassin slow after version upgrade

[Julian Field]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

In which case the SA temp files will be running fast like they were when 
they were in /dev/shm. They are in tmpfs which is what /dev/shm is.

donald.dawson at bakerbotts.com wrote:
> yes, sorry
>
> -----Original Message-----
> From: mailscanner-bounces at lists.mailscanner.info
> [mailto:mailscanner-bounces at lists.mailscanner.info] On Behalf Of Julian
> Field
> Sent: Monday, July 30, 2007 3:20 PM
> To: MailScanner discussion
> Subject: Re: MailScanner/Spamassassin slow after version upgrade
>
>
>
> * PGP Bad Signature, Signed by an unverified key: 07/30/07 at 21:19:31
>
> Just checking, but you do mean tmpfs and not tempfs don't you?
>
> donald.dawson at bakerbotts.com wrote:
>   
>> thanks - already have it mounted as tempfs
>> (/var/spool/MailScanner/incoming).
>>
>> I've attached another sa-debug
>>
>>
>> -----Original Message-----
>> From: mailscanner-bounces at lists.mailscanner.info
>> [mailto:mailscanner-bounces at lists.mailscanner.info] On Behalf Of
>>     
> Julian
>   
>> Field
>> Sent: Monday, July 30, 2007 1:49 PM
>> To: MailScanner discussion
>> Subject: Re: MailScanner/Spamassassin slow after version upgrade
>>
>>
>>
>>     
>>> Old Bad Signature, Signed by an unverified key: 07/30/07 at 19:49:19
>>>       
>>
>> donald.dawson at bakerbotts.com wrote:
>>   
>>     
>>> Max Children = 7
>>> We have a caching DNS server running (named)
>>> Max Unsafe Messages Per Scan = 30
>>> Max Unscanned Messages Per Scan = 30
>>> I've attached output from the debug command.
>>>  
>>> I did change the mix of rule sets - dropped several and added a few.
>>>  
>>> I noticed the incoming emails were creating 
>>> .spamassassin26705z2e3egtmp files (example) in /dev/shm, a ram disk, 
>>> but they are now being created in 
>>> /var/spool/MailScanner/incoming/SpamAssassin-Temp (part of normal 
>>> mounted file system).
>>>     
>>>       
>> Mount /var/spool/MailScanner/incoming with tmpfs for starters, or else
>>     
>
>   
>> change
>> SpamAssassin Temporary Dir = /dev/shm
>> You really should mount ..../incoming with tmpfs as that will make a 
>> significant speed improvement. It's 100% safe.
>>
>>   
>>     
>>>  
>>> dd
>>>
>>>     -----Original Message-----
>>>     *From:* mailscanner-bounces at lists.mailscanner.info
>>>     [mailto:mailscanner-bounces at lists.mailscanner.info] *On Behalf Of
>>>     *Gottschalk, David
>>>     *Sent:* Monday, July 30, 2007 1:02 PM
>>>     *To:* MailScanner discussion
>>>     *Subject:* RE: MailScanner/Spamassassin slow after version
>>>       
> upgrade
>   
>>>     How many children are you running?
>>>      
>>>     Are you running a caching DNS server for SA lookups?
>>>      
>>>     what does 'MailScanner --debug -debug-sa' look like?
>>>      
>>>     One thing that made a difference for me was uping my children
>>>       
> from
>   
>>>     5 to 10. Also lowering my "Max Unsafe Messages Per Scan" to 10,
>>>     and my "Max Unscanned Messages Per Scan" to 10 helped speed
>>>       
> things
>   
>>>     up as well.
>>>      
>>>     Hope that helps.
>>>      
>>>     David Gottschalk
>>>      
>>>
>>>     
>>>       
> ------------------------------------------------------------------------
>   
>>   
>>     
>>>     *From:* mailscanner-bounces at lists.mailscanner.info
>>>     [mailto:mailscanner-bounces at lists.mailscanner.info] *On Behalf Of
>>>     *donald.dawson at bakerbotts.com
>>>     *Sent:* Monday, July 30, 2007 1:44 PM
>>>     *To:* mailscanner at lists.mailscanner.info
>>>     *Subject:* MailScanner/Spamassassin slow after version upgrade
>>>
>>>     The time it takes to process an email has doubled since Friday
>>>     (7/26/07) when I upgraded to MS 4.62.6 and SA 3.2.2.  It was
>>>     around 3.5 seconds, and now it is averaging 7 seconds.
>>>
>>>     We use DCC and razor2 - no pyzor.
>>>
>>>     Jul 30 12:36:35 houmx05 MailScanner[21682]: Batch (30 messages)
>>>     processed in 187.50 seconds
>>>     Jul 30 12:37:06 houmx05 MailScanner[21662]: Batch (16 messages)
>>>     processed in 105.59 seconds
>>>     Jul 30 12:37:24 houmx05 MailScanner[21727]: Batch (30 messages)
>>>     processed in 196.20 seconds
>>>     Jul 30 12:37:28 houmx05 MailScanner[21776]: Batch (30 messages)
>>>     processed in 211.89 seconds
>>>     Jul 30 12:37:38 houmx05 MailScanner[21793]: Batch (30 messages)
>>>     processed in 223.64 seconds
>>>
>>>     sar -u shows idle CPU time:
>>>     12:00:01 AM   CPU    %user    %nice  %system  %iowait    %idle
>>>     Average:          all     10.49      0.00      4.99      1.00    
>>>     83.51
>>>
>>>     # uptime is normal
>>>      12:38:30 up 5 days, 25 min,  1 user,  load average: 0.81, 0.79,
>>>     
>>>       
>> 0.83
>>   
>>     
>>>     I have implemented sa-compile using re2c expecting to get a
>>>     performance boost.
>>>
>>>     'MailScanner --lint' doesn't show any errors, except noting that
>>>     we have clamav processing turned off (output attached).
>>>
>>>     <<ms.txt>>
>>>     I have included output from spamassassin's lint command.
>>>
>>>     /etc/mail/spamassassin contents:
>>>     bakerbotts.cf   - custom local rule file
>>>     Botnet.cf
>>>     Botnet.pm
>>>     init.pre
>>>     init.pre.pre-v310
>>>     KAM.cf
>>>     local.cf
>>>     mailscanner.cf
>>>     pdfinfo.cf
>>>     sare-sa-update-channels.txt
>>>     sa-update-keys
>>>     v310.pre
>>>     v312.pre
>>>     v320.pre
>>>
>>>     contents of sare-sa-update-channels.txt used by
>>>     
>>>       
>> update_spamassassin:
>>   
>>     
>>>     updates.spamassassin.org
>>>     70_sare_adult.cf.sare.sa-update.dostech.net
>>>     70_sare_bayes_poison_nxm.cf.sare.sa-update.dostech.net
>>>     70_sare_evilnum0.cf.sare.sa-update.dostech.net
>>>     70_sare_genlsubj0.cf.sare.sa-update.dostech.net
>>>     70_sare_genlsubj1.cf.sare.sa-update.dostech.net
>>>     70_sare_genlsubj2.cf.sare.sa-update.dostech.net
>>>     70_sare_header.cf.sare.sa-update.dostech.net
>>>     70_sare_highrisk.cf.sare.sa-update.dostech.net
>>>     70_sare_html.cf.sare.sa-update.dostech.net
>>>     70_sare_obfu.cf.sare.sa-update.dostech.net
>>>     70_sare_oem.cf.sare.sa-update.dostech.net
>>>     70_sare_random.cf.sare.sa-update.dostech.net
>>>     70_sare_specific.cf.sare.sa-update.dostech.net
>>>     70_sare_spoof.cf.sare.sa-update.dostech.net
>>>     70_sare_stocks.cf.sare.sa-update.dostech.net
>>>     70_sare_unsub.cf.sare.sa-update.dostech.net
>>>     70_sare_uri0.cf.sare.sa-update.dostech.net
>>>     70_sare_uri1.cf.sare.sa-update.dostech.net
>>>     70_sare_uri2.cf.sare.sa-update.dostech.net
>>>     70_sare_whitelist.cf.sare.sa-update.dostech.net
>>>     70_sare_whitelist_rcvd.cf.sare.sa-update.dostech.net
>>>     70_sare_whitelist_spf.cf.sare.sa-update.dostech.net
>>>     72_sare_bml_post25x.cf.sare.sa-update.dostech.net
>>>     72_sare_redirect_post3.0.0.cf.sare.sa-update.dostech.net
>>>     88_FVGT_headers.cf.sare.sa-update.dostech.net
>>>     99_FVGT_Tripwire.cf.sare.sa-update.dostech.net
>>>     99_sare_fraud_post25x.cf.sare.sa-update.dostech.net
>>>
>>>     Any ideas would be greatly appreciated.
>>>
>>>     Thanks,
>>>     Donald
>>>
>>>     Donald Dawson
>>>     Security Administrator
>>>     Baker Botts L.L.P.
>>>     713-229-2183
>>>
>>>     
>>>       
>> Jules
>>
>>   
>>     
>
> Jules
>
>   

Jules

- -- 
Julian Field MEng CITP
www.MailScanner.info
Buy the MailScanner book at www.MailScanner.info/store

MailScanner customisation, or any advanced system administration help?
Contact me at Jules at Jules.FM

PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654
For all your IT requirements visit www.transtec.co.uk


-----BEGIN PGP SIGNATURE-----
Version: PGP Desktop 9.6.2 (Build 2014)
Charset: ISO-8859-1

wj8DBQFGrkvWEfZZRxQVtlQRAktRAKD4BcLNtZjfGtEUfLmddw+ucn2kOQCfVxSz
tjknqcYSuxAUzfu0YsMDyKs=
=/A7n
-----END PGP SIGNATURE-----

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
For all your IT requirements visit www.transtec.co.uk