Minimum hardware capacity for 35k e-mail scans/day

UxBoD uxbod at splatnix.net
Thu Nov 15 19:49:20 GMT 2007


also what type of filesystem is the Bayes on, if it is in a file, is journaling switched on etc etc ... to be honest since switching it into MySQL I have been very pleased with the performance.

but as everybody says, split out your application types and up the RAM.  RAM is so cheap these days.  I advised the company I am contracted at to go for 8GB RAM.  Its a dual AMD Opteron aswell so I can throw anything at it.  Most messages are pinged at MTA level (love Postfix) and LDAP lookups to LotusNotes.  We process about 150k msgs/pd on both MTAs and we have a load average of 1.2 :)

Regards,

--[ UxBoD ]--
// PGP Key: "curl -s https://www.splatnix.net/uxbod.asc | gpg --import"
// Fingerprint: C759 8F52 1D17 B3C5 5854  36BD 1FB1 B02F 5DB5 687B
// Keyserver: www.keyserver.net Key-ID: 0x5DB5687B
// Phone: +44 845 869 2749 SIP Phone: uxbod at sip.splatnix.net

----- Original Message -----
From: "Glenn Steen" <glenn.steen at gmail.com>
To: "MailScanner discussion" <mailscanner at lists.mailscanner.info>
Sent: Thursday, November 15, 2007 6:45:51 PM (GMT) Europe/London
Subject: Re: Minimum hardware capacity for 35k e-mail scans/day

On 15/11/2007, Edward Prendergast <edward.prendergast at netring.co.uk> wrote:
> > Any advice from the vast pool of MailScanner experience would be greatly
> > appreciated.
>
> >> Are you queues actually building up or are you just concerned with the
> >> load average?
>
> In reply to Greg and Julian:
>
> The queue seems to go up with the load. By the time the load is around 10
> the queue starts to climb without any sign of going down. It usually reaches
> the 300 mark within half an hour to an hour, but has gone up as far as
> 3,000. When I turn bayes off the load goes down and mail queues start
> becoming manageable again.
>
> Our users largely use POP3, with a few using IMAP through squirrelmail.
> Their mailboxes usually tend to contain around 300 messages.
>
> Here's how vmstat looks now with bayes enabled:
> # vmstat 10 5
> procs -----------memory---------- ---swap-- -----io---- --system--
> ----cpu----
>  r  b   swpd   free   buff  cache   si   so    bi    bo   in    cs us sy id
> wa
>  0  5 377144 682732  11324  90488    1    0     4     1    0     0 15  5 70
> 10
>  1 12 377056 723572  12468  94280   47    2  2130   725 1475   795 12  4 45
> 39
>  1  4 376984 668068  15100 101712   53   15  2215   778 1486   759  7  3 50
> 40
>  1  5 377016 704180  13952 108476   56    4  2127  1596 1500   997 11  4 39
> 46

About the only really useful vmstat info is that you have a small swap
activity. si and so should be 0. So the timetested advice "Add more
RAM" holds true for you.
One can guess that a fair amount of I/O is going on, just plain
waiting... Hence the idle values... Investigating that might be
useful. Guess 1) would be bayes (which might be related to locking or
disk IO speed), guess 2) would be network (most likely DNS (caching
only DNS?) or a dead RBL or somesuch).
Oh, I see Steve message. Good thing to try. And add some more RAM...
Or split of some of the workload to another box;-).

> It looks to me like there might be some thrashing going on.

Thrashing is usually an audible phenomenon... Have you been listening
to your HDDs lately?:-).
Some swap activity, yes, but thrashing... Well, perhaps:).

> At this level, the queue looks like this:
> Nov 15 14:32:36 server6 MailScanner[8106]: New Batch: Found 2697 messages
> waiting
> Nov 15 14:32:36 server6 MailScanner[8106]: New Batch: Scanning 10 messages,
> 38032 bytes

Cheers
-- 
-- Glenn
email: glenn < dot > steen < at > gmail < dot > com
work: glenn < dot > steen < at > ap1 < dot > se
-- 
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! 

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.



-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.



More information about the MailScanner mailing list