#1244 Performance enhancement when looking up case-insensitive netgroups
Closed: wontfix 4 years ago by pbrezina. Opened 12 years ago by jhrozek.

There's one slight performance issue here. Lookups in a case-insensitive domain might go to the sysdb more often than strictly necessary. The reason being that if I request "netgroup1" and then "NetGroup1", the second one will not match the hash table and it will go back to the sysdb.

That said, this is definitely an edge-case (and it will still be a local lookup, not a provider check), so the only real downside here is extra wasted memory as we will be keeping two copies of the netgroup info in the hash table.


Fields changed

milestone: NEEDS_TRIAGE => SSSD Deferred

Fields changed

rhbz: => todo

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

7 years 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)

4 years 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/2286

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