On Thu, Jul 31, 2014 at 12:07:18AM +0100, Andrew Beverley wrote:
> On Wed, 2014-07-30 at 22:43 +0000, Viktor Dukhovni wrote:
> > Connection re-use does not prevent concurrency, you'd need a pool
> > of connections or parallel submission processes pulling messages
> > from the application queue. Concurrency is more important than
> > connection re-use.
>
> Ah, okay. Is default_process_limit the correct setting to be looking at
> here? I have it set to the default of 100. The maxproc of the smtp unix
> service in master.cf is set to the default.
You've suddenly switched topics from message injection, for which
the default limits are more than ample to global process limits,
which for an MTA that mostly sends control delivery concurrency.
Did you mean to switch topics? Delivery concurrency is a much more
complex topic, a lot depends on your hardware and network, as well
who you send mail to and how much they push back...
> I notice that maxproc of some other services in master.cf is set to 1 or
> 0, rather than the default of 100 (eg pickup: 1, cleanup: 0, qmgr: 1).
> Is this normal?
Essential. Leave the limits that are 0 or 1 set to 0 or 1. Other
limits are tunable.
--
Viktor.
