Re: DLZ's LDAP driver doesn't use multiple connections

Imri Zvik <[email protected]>
Newsgroups gmane.network.dns.bind9.dlz
Message-ID <[email protected]>
On Tuesday 22 July 2008 15:53:49 Rob Butler wrote:
> Most likely your BIND is compiled as single threaded.  If that's the case,
> there is no need for more than one LDAP connection because there is only
> one thread running within BIND itself.
No, BIND is compiled with multithreading support enabled. I see BIND starting 
multiple threads, and multiple LDAP connections, but actually using only one.

>
> >From the LDAP page on the BIND-DLZ website
> > (http://bind-dlz.sourceforge.net/ldap_driver.html):
>
> The next piece on the line is the number "2".  This parameter is located at
> argv[1] and is required.  This tells BIND how many database connections we
> want the LDAP driver to use.  When BIND is built single threaded, this
> parameter is ignored BUT STILL REQUIRED!  The LDAP driver only uses one
> connection when built for single threaded operation.  When built for
> multithreaded operation, the driver will open the specified number of
> connections and ALWAYS keep them open.  The driver does NOT release
> connections during periods of inactivity and then re-open them when needed.
>  I considered this approach and decided against it.  A DNS server should
> always be ready to answer an onslaught of queries with all of its resources
> available.
>
> Rob
>
>
>
> ----- Original Message ----
>
> > From: Imri Zvik <[email protected]>
> > To: [email protected]
> > Sent: Tuesday, July 22, 2008 4:39:49 AM
> > Subject: [Bind-dlz-testers] DLZ's LDAP driver doesn't use multiple
> > connections
> >
> > Hi,
> >
> > I am trying to understand why I'm getting the worse performance using the
> > LDAP driver.
> >
> > It seems like the LDAP driver is always using one connection, even when
> > it is configured to use more.
> >
> > Even when I loadstress it with multiple clients (querypref running from
> > multiple machines), it is still utilizing only 1 connection.
> >
> > It seems that this is the bottleneck of the LDAP driver... Should it work
> > that way, or is this a bug?
> >
> > -------------------------------------------------------------------------
> > This SF.Net email is sponsored by the Moblin Your Move Developer's
> > challenge Build the coolest Linux based applications with Moblin SDK &
> > win great prizes Grand prize is a trip for two to an Open Source event
> > anywhere in the world
> > http://moblin-contest.org/redirect.php?banner_id=100&url=/
> > _______________________________________________
> > Bind-dlz-testers mailing list
> > [email protected]
> > https://lists.sourceforge.net/lists/listinfo/bind-dlz-testers
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's
> challenge Build the coolest Linux based applications with Moblin SDK & win
> great prizes Grand prize is a trip for two to an Open Source event anywhere
> in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Bind-dlz-testers mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/bind-dlz-testers



-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.