Re^2: Keeping LDAP connections between program runs

[jpfarmer]

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.

[ghenry]

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).

[jpfarmer]

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.

[ghenry]

OK. I would however invest in an upgrade, as things are now very, very fast with the new HDB backend.

I would advise against a switch to Microsoft ADAM, because for the sake of a little easier manangement (and probably quite a bit of Non-standards based LDAP parts), you will lose SO much control for SO much money. A no brainer really as to which to use (as well as the platform it is deployed on).

Getting back to your OP, I would again suggest looking at the server setup.

Just a few thoughts.