389-ds-base

#504 allow turning off name2asi and oid2asi table locks
Closed: wontfix Opened by rmeggins.

Closed: wontfix
Reopen Issue

systemtap analysis shows the name2asi rwlock is heavily contended - rwlocks perform poorly when there is a lot of contention - many customers do not want dynamic schema updates and therefore can live without lock protection - we should introduce a config attribute that allows access to these tables without locking

Metadata Update from @lkrispen:
- Issue assigned to lkrispen
- Issue set to the milestone: 1.3.0

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

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)
Metadata
None
None
None
Normal
ack
RHCust
0
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.