SSSD / sssd

#2882 Comparison between talloc and talloc_pool
Closed: wontfix by pbrezina. Opened by pcech.

Closed: wontfix
Reopen Issue

It would be useful to measure the difference between talloc() and talloc_pool().
Documentation: https://talloc.samba.org/talloc/doc/html/libtalloc__pools.html
Hints: perf, callgrind on nss unit test.

Part of the 1.14 performance enhancements.

It make sense to to measure the difference between talloc() and talloc_pool() only with real use-case.

It's not very useful to write an artificial "simple C program". So the subject of ticket should be changed.
or description of ticket should extended.

The original plan was to try it on nss unit test.

Since Pavel already did some experiments in this area, this ticket has lower priority. But I still think it might be a good idea to run a couple of tests on the responders only. Using pools for providers is out of scope.

milestone: NEEDS_TRIAGE => SSSD 1.14 beta

Fields changed

rhbz: => 0

I still think it would be good to run some measurements, but I suspect there won't be time in 1.14..

milestone: SSSD 1.14 beta => SSSD 1.14 backlog

Linked to Bugzilla bug: https://bugzilla.redhat.com/show_bug.cgi?id=1373547 (Red Hat Enterprise Linux 7)

rhbz: 0 => [https://bugzilla.redhat.com/show_bug.cgi?id=1373547 1373547]

Since the 1.14 branch is transitioning into maintenance mode and new functionality is being developed in master which will become 1.15 eventually, I'm mass-moving tickets from the 1.14 backlog milestone to the "Future releases" milestone.

milestone: SSSD 1.14 backlog => SSSD Future releases (no date set yet)

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

Metadata Update from @jhrozek:
- Custom field design_review reset (from 0)
- Custom field mark reset (from 0)
- Custom field patch reset (from 0)
- Custom field review reset (from 0)
- Custom field sensitive reset (from 0)
- Custom field testsupdated reset (from 0)
- Issue close_status updated to: None
- Issue tagged with: performance

Metadata Update from @thalman:
- Custom field design_review reset (from false)
- Custom field mark reset (from false)
- Custom field patch reset (from false)
- Custom field review reset (from false)
- Custom field sensitive reset (from false)
- Custom field testsupdated reset (from false)
- Issue tagged with: Canditate to close

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)

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/3923

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.
Metadata
None

Candidate to close performance

None
None
High
false
false
false
task
SSSD
1.13.2
https://bugzilla.redhat.com/show_bug.cgi?id=1373547
false
false
false
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.