On 07/06/2010 01:10 PM, Victor Duchovni wrote:
So you have multiple exit points with non-uniform latency, but the more
severe congestion is downstream, so you want to load the exit points
uniformly. Yes, the solution is to disable the connection cache, and
set reasonably low connection and helo timeouts in the transport feeding
the two exit points, so that when one is down and non-responsive (no TCP
reset), you don't suffer excessive hand-off latency for 50% of deliveries.
I did that.
You know what? It's amazingly accurate actually. After tens of thousands
of messages, the logs on the two exit points showed almost exactly the
same amount of messages relayed - within 1.2% or so. That was a very
nice result to contemplate.
After disabling the connection cache for internal delivery, it looks
like we took a 2x performance hit internally, which is exactly what I
expected. But that's ok, the internal rate is orders of magnitude above
the Yahoo rate anyway. From an external perspective, things are actually
much better now.
Case closed. Thanks for all the help.
--
Florin Andrei
http://florin.myip.org/
