John Baker:
> On 04/25/2011 10:59 AM, Victor Duchovni wrote:
> > On Thu, Apr 21, 2011 at 02:59:27PM -0400, John Baker wrote:
> >
> >> There are several ways to make this work right including virtual aliases
> >> but the cleanest way seemed to me to be a per user transport map lookups
> >> for cloud users.
> > I think that per-user transport lookups are unwise.
>
> Hi,
>
> Thanks for the reply, could you tell me why per-user transports are
> unwise? Do they not scale well? Our numbers are fairly low.
The problem is that these lookups happen for each delivery, on
request by the queue manager.
If you're doing per-user entries they will almost always be pulled
from a "network" database such as LDAP or *SQL, and those lookups
can become a queue manager performance bottleneck. This hurts
because there is only one queue manager process.
If you're doing domain-based transport mapping, the mapping can be
kept in a local file (hashed, a la Berkeley DB) and latency will
not be an issue.
Wietse
