-
Notifications
You must be signed in to change notification settings - Fork 89
-
Notifications
You must be signed in to change notification settings - Fork 89
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
allow turning off vattr lookup in search entry return #511
Comments
Comment from mreynolds (@mreynolds389) at 2012-12-13 02:03:26 attachment |
Comment from mreynolds (@mreynolds389) at 2012-12-13 03:47:25 git merge ticket511 [mareynol@localhost replication]$ git push origin master |
Comment from nkinder (@nkinder) at 2013-03-07 00:15:27 Ticket has been cloned to Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=918705 |
Comment from mreynolds (@mreynolds389) at 2013-05-08 03:11:24 Remove Slapi_Counter to store the ncofnig setting |
Comment from mreynolds (@mreynolds389) at 2013-05-08 20:50:50 git merge ticket511 git push origin master commit b3d2ee0 |
Comment from mreynolds (@mreynolds389) at 2017-02-11 23:05:36 Metadata Update from @mreynolds389:
|
Comment from tbordaz (@tbordaz) at 2018-07-30 10:48:17 Just for recording, I think this ticket was impacted by glibc issue https://bugzilla.redhat.com/show_bug.cgi?id=200247 |
Comment from tbordaz (@tbordaz) at 2018-07-30 10:48:18 Metadata Update from @tbordaz:
|
Cloned from Pagure issue: https://pagure.io/389-ds-base/issue/511
systemtap and callgrind analysis show a lot of time spent in vattr_map_namespace_sp_getlist and slapi_vattr_namespace_values_get_sp - every time a search entry is compared against a search filter, and then again when the entry is sent to the client, to see if there are any virtual attributes to add - if a user does not want or care about virtual attributes at all, there should be a way to turn off this vattr checking using a config attribute
The text was updated successfully, but these errors were encountered: