On Tue, 7 Dec 2004, Chris Edwards wrote:
>
> Sort of related, as well as smtp_accept_max, we set smtp_accept_max_per_host
> to a low value (currently 5 over each of 2 MXs).
Our settings are currently:
smtp_accept_max_per_host = 10
deliver_queue_load_max = 20.00
queue_only_load = 10.00
queue_run_max = 20
smtp_accept_max = 400
smtp_accept_reserve = 20
smtp_load_reserve = 15.00
smtp_reserve_hosts = +relay_hosts
The load settings are based on the load imposed by MailScanner, which is
running up to 7 concurrent SpamAssassins or anti-virus scanners.
The smtp_accept_max setting is twice what we need at the moment, because I
haven't adjusted it after reducing our callout timeouts. Callouts are a
big contributor to high concurrency. 400 is perhaps a bit high for lots of
less-idle processes.
I should note that we have 7 machines and deal with up to 1.5 million
connections each day.
Tony.
--
<fanf@???> <dot@???>
http://dotat.at/ ${sg{\N${sg{\
N\}{([^N]*)(.)(.)(.*)}{\$1\$3\$2\$1\$3\n\$2\$3\$4\$3\n\$3\$2\$4}}\
\N}{([^N]*)(.)(.)(.*)}{\$1\$3\$2\$1\$3\n\$2\$3\$4\$3\n\$3\$2\$4}}
