Viktor Dukhovni:
> > We would like to use Per-Destination Connection Caching to increase
> > our throughput for "outlook:".
>
> No, you *do not* want to do that. That can increase connection
> concurrency beyond your process limit, in the form of idle connections
> that have a different nexthop than the one to which you're currently
> delivering email.
We could fix these excess connections by grouping cached connections
by transport, and by evicting a cached connection for some transport
if a requested connection for that transport is not found.
It's not optimal from a reuse point of view, but it ensures that
one transport cannot exceed the number of connections determined
by its process limit.
Wietse
