in reply to Keeping LDAP connections between program runs

How many binds are we talking about here?

LDAP is designed for the sole purpose of high read requests, so if you are just requesting a read, be it TLS/Start_TLS or SASL, I suggest you have a word with the guys who setup the server. That could be the main problem.

Just a thought.

Walking the road to enlightenment... I found a penguin and a camel on the way.....
Fancy a yourname@perl.me.uk? Just ask!!!
  • Comment on Re: Keeping LDAP connections between program runs

Replies are listed 'Best First'.
Re^2: Keeping LDAP connections between program runs
by jpfarmer (Pilgrim) on Aug 30, 2005 at 22:57 UTC

    At high load, about 3000 binds/hour. They're simple binds; there's a SSH tunnel between the server and the client so we could avoid the overhead of SASL.

[reply]

      Not that many, compared to some places

      Please don't tell me you are using a ldbm backend? I hope it's a bdb (if you are using OpenLDAP that is).

      Walking the road to enlightenment... I found a penguin and a camel on the way.....
      Fancy a yourname@perl.me.uk? Just ask!!!
[reply]

        True, but we're not the only client going against the server. Some other far more mission-critical services are generating at least as many hits as we are, so the numbers add up. We use a master node with a few replicas and this application is hitting one of the replicas.

        And yes, we're using BDB. Unfortunatly, we're using a fairly old version of OpenLDAP. We hope to switch to ADAM as soon as the next version is released, which should be the end of the calendar year.

[reply]

In Section Seekers of Perl Wisdom