Maximum Processing Attempts

[Julian Field]

Can someone test this please? How much of a difference does it really make?

It is a few small SQL operations per message on a very fast lightweight 
(if any SQL server is lightweight!) database that will be in memory 
anyway. I have specifically switched off fsyncs when it writes to the 
database, so it shouldn't result in any appreciable disk i/o at all.

Should I leave it switched on by default, so heavily loaded sites can 
switch it off to gain that extra bit of performance, at the cost of a 
potential reliability hit?
If we go for that, can someone please edit the "optimising tips" wiki 
page for me?

Thanks folks!
Jules.

P.S. Have you seen I am on twitter too these days? You too can get to 
see my inane ramblings at twitter.com/JulesFM.

On 27/04/2009 22:24, Christiaan den Besten wrote:
> Does it realy hit performance noticably? ..... in normal behaviour the 
> database is extremly small .... so it should probably always live in 
> disk-cache. And if people want to be sure, they can place it on tmpfs, 
> doesn't hurt if it gets lost :)
>
> We have seen 'our share of broken messages' that trashed some of our 
> servers, .... would have loved to have had the processing database 
> back then :) :)
>
> bye,
> Chris
>
> ----- Original Message ----- From: "Julian Field" 
> <MailScanner at ecs.soton.ac.uk>
> To: "MailScanner discussion" <mailscanner at lists.mailscanner.info>
> Sent: Sunday, April 26, 2009 20:28
> Subject: Maximum Processing Attempts
>
>
>> Please can someone add an entry into the wiki about this 
>> MailScanner.conf option and its compatriot "Processing Attempts 
>> Database".
>>
>> As requested, I'm going to make this option disabled by default, as 
>> it has a speed impact, so people need to know it exists if they get 
>> any messages that kill MailScanner and therefore need to enable it.
>>
>> Unless people think I should leave it enabled of course... (your 
>> votes are welcome)
>>
>> Many thanks!
>>
>> Jules
>>
>> -- 
>> Julian Field MEng CITP CEng
>> www.MailScanner.info
>> Buy the MailScanner book at www.MailScanner.info/store
>>
>> Need help customising MailScanner?
>> Contact me!
>> Need help fixing or optimising your systems?
>> Contact me!
>> Need help getting you started solving new requirements from your boss?
>> Contact me!
>>
>> PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654
>> Follow me at twitter.com/JulesFM
>>
>>
>> -- 
>> This message has been scanned for viruses and
>> dangerous content by MailScanner, and is
>> believed to be clean.
>>
>> -- 
>> 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! 
>

Jules

-- 
Julian Field MEng CITP CEng
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
PGP public key: http://www.jules.fm/julesfm.asc


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