Martin Gregorie-2 wrote: > > Its reliable enough, but concurrency will be limited by the number of > child processes you allow spamd to run - on normal MTAs this limit is in > single or low double figures. To allow 'hundreds' of simultaneous tests > you'd have to launch a copy of spamassassin as each message is > submitted, which means also providing enough hardware to run 'hundreds' > of copies of spamassassin in parallel.
Where do I limit/configure the number of child processes that spamd can run? Can you provide me documentation link for the same? Can you share with me the normal limit imposed by a typical MTA? Martin Gregorie-2 wrote: > > Take a good look at your existing SA installation(s) and scale the mail > checking installation accordingly: its just a normal hardware sizing > exercise based round an application that requires fairly significant > resources (memory and cpu) to process each submitted message. If you were in my place, what would you recommend me to check with incase of SA installation? -- View this message in context: http://old.nabble.com/Stability-of-spamassassin-command-line-tool-tp29171831p29172749.html Sent from the SpamAssassin - Users mailing list archive at Nabble.com.
