On 08/04/2015 11:57 AM, ghiureai wrote:
We are seeing poor performance from LDAP retrieving 2500-4500 entries compare with one of our regular RDBMS , here is bellow the result for a ldapsearch.
We are questioning if for general cn=(.*..) search string , LDAP has to run  a round trip for each  subset result entry ?

What cfg needs tuned to  see some performance improvements beside  cache mem size ?
There isn't any, besides indexing, and by default cn is indexed for substring searches.

Can you provide the output from the access log during one of these searches? 

ldapsearch -x -s one -H  -b 'ou=Groups,ou=ds,dc=cxxx,dc=net' -W -D 'uid=xx,ou=Users,ou=ds,dc=cxxxr,dc=net' 'cn=*MT*' 'cn, nsaccountlock'
# search result
search: 2
result: 0 Success

# numResponses: 2608
# numEntries: 2607

real    0m19.284s
user    0m0.040s
sys    0m0.052s

389 users mailing list