{**possible spam detected**} RE: performance testing new server, results

[Res]

On Wed, 21 Feb 2007, Chris Yuzik wrote:

> As it stands right now, my guess is that this server will handle about 100 
> messages per minute without too many complaints, given the current 
> configuration. We don't currently see anywhere near this, but it's nice to 
> know we've got the overhead.

By fine tunning spamassassin you'll increase this dramatically, the 
biggest problem I found was dcc/pyzor/razor they add lots of time, 
when disabled even with a lot of local rules things improved out of sight, 
we do now use razor on some machines.

Your looking at maybe 2 messages every second, we've run similar hardware 
on front ends (HP DL380G5's with 4 G ram) that do 6 to 15 (depending on 
time of day) per second, changing batch size to 50 removed any backlog, using
tmpfs and spearate spool and log dirs we never see a load of above 1.5
However this is using f-prot, clam yielded loads of up to 5 and 
clamavmodule bailed for some unknown reason when it has a sh1teload of 
work, mind you not used it in some time now, because with f-prot, its
a perfect setup, sure to use it in this environment it's not free like 
clamav, but you'll not regret the cost outlay.



> would be great to have something that logs the number of messages hitting our 
> server per minute, average time in the queue, etc. I realize that we can turn 
> on speed logging in the MailScanner.conf file, but manually going through the

http://mailscannermrtg.sourceforge.net   is pretty close to what you 
want.


-- 
Cheers
Res

"We can be Heroes, just for one day" - Davey (Jones) Bowie