RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:

During search rate, the server checks that the base search is not a referral (attribute 'ref').
Most of the time this check is useless as the base entry is not a referral. The checking of the entry is expensive. Improving this tests improves searchrate by 5%

(gdb) where
0  0x00007f46038ac470 in attrlist_find 
1  0x00007f46038c6046 in slapi_entry_attr_find 
2  0x00007f45f599f97e in check_entry_for_referral 
    at ldap/servers/slapd/back-ldbm/findentry.c:35
3  0x00007f45f599fe5f in find_entry_internal_dn 
4  0x00007f45f599fe5f in find_entry_internal 
    at ldap/servers/slapd/back-ldbm/findentry.c:322
5  0x00007f45f599fe5f in find_entry_internal 
    at ldap/servers/slapd/back-ldbm/findentry.c:302
6  0x00007f45f59a02bf in find_entry 
7  0x00007f45f59d05b4 in ldbm_back_search 
8  0x00007f46038fec2b in op_shared_search 
9  0x000055a1fe0278f3 in do_search 
10 0x000055a1fe01525d in connection_dispatch_operation 
11 0x000055a1fe01525d in connection_threadmain 
12 0x00007f460123e568 in _pt_root 
13 0x00007f4600bd8322 in start_thread 
14 0x00007f4600367823 in clone 

0

Upstream ticket:

https://github.com/389ds/389-ds-base/issues/4308

As per comment #c5 marking as VERIFIED.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (389-ds-base bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2023:2274