Extracting those last drops of performance
Martin Hepworth
maxsec at gmail.com
Wed May 5 14:44:00 IST 2010
On 5 May 2010 13:10, Steve Freegard <steve.freegard at fsl.com> wrote:
> On 04/05/10 17:44, Zaeem Arshad wrote:
>
>> I am using caching dns, ram disk for processing, clamd, compiled
>> spamassassin rules and optimized scheduler and filesystems in this
>> server. Any ideas on how I can tweak the above settings to gain more
>> MailScanner performance?
>>
>
> Set 'Log Speed = yes' in MailScanner.conf; then plot the average time spent
> per message. This is the key metric when tuning; it should be < 10 seconds
> and preferably 2-3 secs.
>
> That's the most important thing to do *first*. That way you can measure
> the difference once any tuning has been done.
>
> By far the most heavyweight process is going to be SpamAssassin - so that's
> most likely the area you are going to need to focus on. Are you using
> Bayes? If so - using which storage method?
>
> Regards,
> Steve.
>
> --
> MailScanner mailing list
> mailscanner at lists.mailscanner.info
> http://lists.mailscanner.info/mailman/listinfo/mailscanner
>
> Before posting, read http://wiki.mailscanner.info/posting
>
> Support MailScanner development - buy the book off the website!
>
Also have a look at the "getting the most out of spamassassin" and the
performance tuning (just above the getting the most on the same page). It's
a little dated but does give some pointers to get you started.
makeing sure you're only hitting RBLS you have local zone transfers for etc
will help alot if you've not already done that.
--
Martin Hepworth
Oxford, UK
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.mailscanner.info/pipermail/mailscanner/attachments/20100505/510741fd/attachment.html
More information about the MailScanner
mailing list