Am 21.04.2017 um 16:08 schrieb Viktor Dukhovni:
> Message injection via sendmail(1) is much less efficient than injection
> via SMTP.  The message is synced to disk twice, and the pickup(8) service
> can only process one message at a time, while SMTP inject can handle
> multiple messages in parallel.

I'm aware of that. But (I think) submission is not the problem to me: The 
script take seconds only.
but then the messages are visible in the active queue. postfix start relaying 
to the MSA
one by one message up to $relay_destination_concurrency_limit (20) parallel.

> You've provided no information on where the performance bottleneck lies.
> What are the averages of the delays=a/b/c/d log values?
can look on Monday for these values....

> Sure, and connection re-use is mainly helpful when some of the IP addresses
> of the SMTP servers for the nexthop domain are non-responsive and connections
> are timing out.
that's not the case

> Otherwise, connection caching offers only marginal gains.
> (If PTR records for your client's IP address are registered at a 
> non-responsive
> DNS server, that could be another source of per-connection overhead).
also not happen here

>> as expected, even "smtp_connection_cache_destinations = static:all" doesn't 
>> help.
>>
>> So what may be the strategy to speed up?
> 
> First identify the origin of the delays.  Lack of connection reuse is rarely
> the problem.
> 
> See:
> 
>       http://www.postfix.org/TUNING_README.html
>       http://www.postfix.org/QSHAPE_README.html
> 
OK, will read again, Thanks

One point to answer Wietse's suggestion: "Sending MULTI-RECIPIENT messages"
That's impossible because every message contain unique content for the
specific receiver. ( really 10k /different/ messages )

Andreas

Reply via email to