Currently to find a new connection we attempt to iterate from the start of the connection table until we succeed in locking a connection and asserting it is free.
This is really slow, contends locks and could take a long time on busy servers.
Instead we should have a freelist of pointers into the connection table that we can "grab" from and when we are complete, we can "return to".
Metadata Update from @mreynolds: - Custom field origin adjusted to None - Custom field reviewstatus adjusted to None - Issue set to the milestone: 1.4.3
https://pagure.io/389-ds-base/pull-request/50788
Metadata Update from @tbordaz: - Issue set to the milestone: None (was: 1.4.3)
Metadata Update from @vashirov: - Issue set to the milestone: 1.4.3
Metadata Update from @firstyear: - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)
Followup of PR, a performance improvement was identified in cn=monitor. Ticket https://pagure.io/389-ds-base/issue/50906 will track it
0e6a04a..d98699a master
389-ds-base is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in 389-ds-base's github repository.
This issue has been cloned to Github and is available here: - https://github.com/389ds/389-ds-base/issues/3841
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix (was: fixed)
Login to comment on this ticket.