389-ds-base

#49732 Optimize resource limit checking for rootdn issued searches
Closed: wontfix Opened by mreynolds.

Closed: wontfix
Reopen Issue

Issue Description

When performing a search as the Directory Manager resource limits should not apply. So there is no need to "get" the limits if its a Directory Manager initiated search. I'm seeing around 2% performance increase when we skip getting the resource limits. It's not much, but it's something.

https://pagure.io/389-ds-base/pull-request/49733

Metadata Update from @mreynolds:
- Custom field component adjusted to None
- Custom field origin adjusted to None
- Custom field reviewstatus adjusted to review
- Custom field type adjusted to None
- Custom field version adjusted to None

Had to create new PR:

https://pagure.io/389-ds-base/pull-request/49750

commit 67efef0742fd4851c2e41a4ed1c0cb142c1047e9

Metadata Update from @mreynolds:
- Issue close_status updated to: fixed
- 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/2791

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