#50786 Connection Table freelist
Closed: wontfix 2 years ago by firstyear. Opened 2 years ago by firstyear.

Issue Description

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

2 years ago

Metadata Update from @tbordaz:
- Issue set to the milestone: None (was: 1.4.3)

2 years ago

Metadata Update from @vashirov:
- Issue set to the milestone: 1.4.3

2 years ago

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

2 years ago

Followup of PR, a performance improvement was identified in cn=monitor. Ticket https://pagure.io/389-ds-base/issue/50906 will track it

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.

Thank you for understanding. We apologize for all inconvenience.

Metadata Update from @spichugi:
- Issue close_status updated to: wontfix (was: fixed)

a year ago

Login to comment on this ticket.

Metadata