Performance numbers for a DELL R710
Martin Hepworth
maxsec at gmail.com
Wed Jun 3 08:58:46 IST 2009
more children will help - alot of this is suck it and see as
performance can vary alot. normal starting point is 5 children per
core and 30 messages per batch.
for that sort of level I'd be looking at multiple machines - if you
loose this machine or whatever reason what happens!
Also check the RBL's you're running - things like spamhaus will
require a licence for thsi sort of amount and too RBLs slows the
processing down alot.
--
Martin Hepworth
Oxford, UK
2009/6/3 Zaeem Arshad <zaeem.arshad at gmail.com>:
>
>
> On Wed, Jun 3, 2009 at 12:47 AM, Martin Hepworth <maxsec at gmail.com> wrote:
>>
>> Zaeem
>>
>> nice.
>>
>> depends on the tests you run (RBLs etc) and the size of the emails.
>>
>> look in the wiki for performance and tuning on both MailScanner and
>> Spamassassin.
>
> I have a test box with the same specs but 8 Gigs of RAM. My performance
> tuning so far has been
>
> - tmpfs for message scanning
> - DNS caching server on the same box
> - Lower timeouts on Postfix (another instance handling retries)
> - Compiled rules on SA
> - DCC, Razor
> - Clamd
> - Asyncrhonous logging
>
> Filesystem underneath is XFS and average mailsize is around 60KB. I have
> pretty much made all the changes suggested and currently the server is
> handling around 45000 emails/hour. Do you think increasing the number of
> MailScanner children might help? What other performance tweaks can I have? I
> am looking to scale the system to handle at least 65 emails/second with
> antivirus, antispam scanning and RBL checks.
>
>
> --
> Zaeem
>
>
> --
> 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!
>
>
More information about the MailScanner
mailing list