On 08/04/2015 12:53 PM, German Parente wrote:
----- Original Message -----
From: "Mark Reynolds" <mareynol@xxxxxxxxxx>
To: "General discussion list for the 389 Directory server project." <389-users@xxxxxxxxxxxxxxxxxxxxxxx>
Sent: Tuesday, August 4, 2015 6:04:17 PM
Subject: Re: 389-DS poor performance retrieving groups
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?
Seems that by default, substring indexing is done on lenght 3.
But "*" counts as part of the key (*mt, mt*), so it should be indexed
So, probably the keys with lenght 2 will provoke this search to be unindexed.
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 389-users@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/389-users
--
389 users mailing list
389-users@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/389-users
--
389 users mailing list
389-users@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/389-users
