[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Re: Index Alias Attribute
- To: Josh Catana <jcatana@gmail.com>
- Subject: Re: Index Alias Attribute
- From: Hallvard Breien Furuseth <h.b.furuseth@usit.uio.no>
- Date: Fri, 14 Jul 2017 17:41:21 +0200
- Cc: openldap-technical@openldap.org
- Content-language: en-MW
- In-reply-to: <CAJOKg0TkTSHdWZ0Pgt6zrNoF1O+mbUWyJK=F4WsHzY8HbUFzgQ@mail.gmail.com>
- References: <CAJOKg0TkTSHdWZ0Pgt6zrNoF1O+mbUWyJK=F4WsHzY8HbUFzgQ@mail.gmail.com>
- User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.2.0
On 13. juli 2017 16:35, Josh Catana wrote:
We heavily rely on aliases to different OUs to manage access to different
environments, prod/dev/qa/etc.
Don't. Having lots of aliases cancels out the effect of your indexes:
Looking at what it's doing it spending a lot of time with bld_idl_union in
the BDB backend.
(...)
Is this because it has to join aliases to actual CNs?
Yes. Indexing does not look "through" an alias, so a search which
follows aliases must follow every alias in the search scope in order
to check each aliased entry with the filter.
Can I index the alias attribute and if I do would it help performance?
Nope. The best you can do is to index objectClass, which you should.
That tells slapd which entries are alias entries, referral entries etc.
--
Hallvard