389-ds-base

#49414 multi queue nunc-stans
Closed: wontfix by mreynolds. Opened by firstyear.

Closed: wontfix
Reopen Issue

Issue Description

To prevent bottlenecks on the NS event queues, we should split this to have many smaller pools with unique locks - this prevents starvation of jobs, and reduces contention.

We should check if we can do thread pinning for numa regions in this patch also,

From studies by openldap they saw 8 - 16 threads per group was the best number, but we should test this ourselves too,

Metadata Update from @mreynolds:
- Custom field component adjusted to None
- Custom field origin adjusted to None
- Custom field reviewstatus adjusted to None
- Custom field type adjusted to None
- Custom field version adjusted to None
- Issue set to the milestone: 1.4 backlog

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

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

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