Performance: Ruby/LDAP vs. ActiveLDAP vs. Net::LDAP

Hi everyone,
Currently, in an application I’m working on I’m using Ruby/LDAP and
ActiveLDAP - and they both work relatively well. But recently I’ve run
into some performance snags. So my question is - is there a large
performance gap between Ruby/LDAP, ActiveLDAP, and Net::LDAP that would
justify standardizing on one over the others?

On 10/11/06, [email protected] [email protected] wrote:

Hi everyone,
Currently, in an application I’m working on I’m using Ruby/LDAP and
ActiveLDAP - and they both work relatively well. But recently I’ve run
into some performance snags. So my question is - is there a large
performance gap between Ruby/LDAP, ActiveLDAP, and Net::LDAP that would
justify standardizing on one over the others?

ActiveLDAP is a wrapper on top of Ruby/LDAP. There is supposed to be
work later toward making ActiveLDAP work with Net::LDAP, but I don’t
think that’s started yet. Net::LDAP is pure Ruby, which means its
significantly more portable. IMO, Net::LDAP has the better LDAP API
than Ruby/LDAP (which mirrors the C API faithfully).

-austin

On 10/11/06, [email protected] [email protected] wrote:

Hi everyone,
Currently, in an application I’m working on I’m using Ruby/LDAP and
ActiveLDAP - and they both work relatively well. But recently I’ve run
into some performance snags. So my question is - is there a large
performance gap between Ruby/LDAP, ActiveLDAP, and Net::LDAP that would
justify standardizing on one over the others?

Do you have test-cases and benchmarks?

From what I can see, most Ruby users are using Net::LDAP to authenticate
users, and most of those are binding against Active Directory.
Relatively
few people are doing bulk-queries where performance problems would be
readily apparent. I have made some performance-improvements to Net::LDAP
recently but didn’t get too aggressive about it because the use-cases
don’t
justify it. But again, tell me more about what you’re trying to do.

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs