[Date Prev][Date Next]
RE: (ITS#7610) scope index isn't used correctly with the filter index
- To: openldap-its@OpenLDAP.org
- Subject: RE: (ITS#7610) scope index isn't used correctly with the filter index
- From: email@example.com
- Date: Tue, 28 May 2013 16:26:17 GMT
- Auto-submitted: auto-generated (OpenLDAP-ITS)
> Date: Tue, 28 May 2013 16:13:29 +0000
> From: firstname.lastname@example.org
> To: email@example.com
> Subject: Re: (ITS#7610) scope index isn't used correctly with the filter index
> firstname.lastname@example.org wrote:
>> Full_Name: Meike Stone
>> Version: 2.4.33
>> OS: Linux
>> URL: ftp://ftp.openldap.org/incoming/
>> Submission from: (NULL) (22.214.171.124)
>> I have a directory with about 2,000,000 objects at all.
>> In one conteiner (basedn for search) are about 84,000 objects
>> but only one of this is a person with objectclass=inetOrgperson.
>> I have about 420,000 objectclass=inetOrgperson.
>> The search with the specified basedn where only the one inetOrgperson
>> is located needs about 5 minutes ...
>> see: http://www.openldap.org/lists/openldap-technical/201305/msg00210.html
> Sorry, digging further into the code I see I was mistaken. The two indices are
> being combined correctly and the code works in my own tests.
> The search looks up the scope index (IDs of all the entries in the target
> scope) and the filter indices and computes their intersection. Not sure why
> this would be so slow in your case.
This sounds very similar to problem I was having, and I had to increase BDB_IDL_LOGN to 18 for the (rebuilt) objectclass index to be used.