Bug 52175 - Use "sortvals" for uniqueMember and memberUid to improve performance of group membership changes
Use "sortvals" for uniqueMember and memberUid to improve performance of group...
Status: NEW
Product: UCS
Classification: Unclassified
Component: LDAP
UCS 4.4
Other Linux
: P5 normal with 1 vote (vote)
: ---
Assigned To: UCS maintainers
UCS maintainers
:
Depends on:
Blocks: 57065
  Show dependency treegraph
 
Reported: 2020-10-02 10:07 CEST by Arvid Requate
Modified: 2024-02-16 12:00 CET (History)
1 user (show)

See Also:
What kind of report is it?: Development Internal
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional): Large environments, UCS Performance
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Arvid Requate univentionstaff 2020-10-02 10:07:02 CEST
We should check, if we can improve the performance of modifications to large groups by using the sortvals parameter on uniqueMember and memberUid. The comment https://bugs.openldap.org/show_bug.cgi?id=9349#c6 recommends this.

       sortvals <attr> [...]
              Specify  a  list of multi-valued attributes whose values will always be maintained in sorted order. Using this option will allow Modify, Compare, and filter
              evaluations on these attributes to be performed more efficiently. The resulting sort order depends on the attributes' syntax and matching rules and may  not
              correspond to lexical order or any other recognizable order.