#3471 RFE: lazy parsing of object received from LDAP
Closed: wontfix a year ago by pbrezina. Opened 3 years ago by jhrozek.

Currently we always parse the full LDAP object regardless of whether we will use all atributes. Quite often, we receive the LDAP object, parse only the name and the timestamp, then bump the timestamp cache and we're done.

It would improve performance if we instead parsed the attributes on-demand.


Metadata Update from @jhrozek:
- Issue tagged with: RFE, performance

3 years ago

Metadata Update from @jhrozek:
- Issue set to the milestone: SSSD 1.16.0

3 years ago

Metadata Update from @jhrozek:
- Issue priority set to: major

3 years ago

Since we are required to release a new upstream tarball no later than Friday Oct-20, I'm moving tickets that will not be closed by that date to the next milestone, 1.16.1

Metadata Update from @jhrozek:
- Issue set to the milestone: SSSD 1.16.1 (was: SSSD 1.16.0)

3 years ago

Metadata Update from @jhrozek:
- Issue tagged with: postpone-to-2-0

3 years ago

Metadata Update from @jhrozek:
- Issue untagged with: postpone-to-2-0
- Issue set to the milestone: SSSD 2.0 (was: SSSD 1.16.1)

3 years ago

Metadata Update from @jhrozek:
- Issue priority set to: minor (was: major)

3 years ago

Metadata Update from @jhrozek:
- Issue set to the milestone: SSSD 2.1 (was: SSSD 2.0)

2 years ago

Metadata Update from @jhrozek:
- Issue set to the milestone: SSSD 2.2 (was: SSSD 2.1)

2 years ago

Metadata Update from @jhrozek:
- Issue set to the milestone: SSSD 2.3 (was: SSSD 2.2)

2 years ago

Metadata Update from @thalman:
- Issue tagged with: Canditate to close

a year ago

Thank you for taking time to submit this request for SSSD. Unfortunately this issue was not given priority and the team lacks the capacity to work on it at this time.

Given that we are unable to fulfill this request I am closing the issue as wontfix.

If the issue still persist on recent SSSD you can request re-consideration of this decision by reopening this issue. Please provide additional technical details about its importance to you.

Thank you for understanding.

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

a year 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/4497

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