Re: (ITS#7610) scope index isn't used correctly with the filter index

[meike.stone@googlemail.com]

2013/5/28 Howard Chu <hyc@symas.com>:
> meike.stone@googlemail.com wrote:
>>
>> Full_Name: Meike Stone
>> Version: 2.4.33
>> OS: Linux
>> URL: ftp://ftp.openldap.org/incoming/
>> Submission from: (NULL) (193.200.138.3)
>>
>>
>> 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.

hmm, while search, the one entry with the objectclass is shown
immediately, but then, it takes a long time to "recognize" that that
is all ...

How does the slapd calculate/determine the scope index?

Tomorrow I try to check this in test environment ..
Are there any special things/hints I can test or see?

Thanks Meike