#3409 Optimize IPA-specific LDAP searches to improve performance
Closed: duplicate 2 months ago by pbrezina. Opened 3 years ago by jhrozek.

389-DS builds 'candidate lists' of potential matches from 'left-to-right', so it makes sense for the first component of the LDAP search to be the most specific.

Bad:
"(&(objectClass=ipaOverrideAnchor)(ipaAnchorUUID=:SID:S-XYZ-ABC))"

Good:
"(&(ipaAnchorUUID=:SID:S-XYZ-ABC)(objectClass=ipaOverrideAnchor))"

Note that this optimization only makes sense for 389-DS as we have no idea what other LDAP servers might be doing.


Metadata Update from @jhrozek:
- Issue set to the milestone: SSSD Future releases (no date set yet)

2 years ago

Metadata Update from @pbrezina:
- Issue close_status updated to: duplicate
- Issue status updated to: Closed (was: Open)

2 months ago

SSSD is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in SSSD's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/SSSD/sssd/issues/4436

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Login to comment on this ticket.

Metadata