Bug 52175

Summary:	Use "sortvals" for uniqueMember and memberUid to improve performance of group membership changes
Product:	UCS	Reporter:	Arvid Requate <requate>
Component:	LDAP	Assignee:	UCS maintainers <ucs-maintainers>
Status:	NEW ---	QA Contact:	UCS maintainers <ucs-maintainers>
Severity:	normal
Priority:	P5	CC:	best
Version:	UCS 4.4
Target Milestone:	---
Hardware:	Other
OS:	Linux
See Also:	https://forge.univention.org/bugzilla/show_bug.cgi?id=48545 https://forge.univention.org/bugzilla/show_bug.cgi?id=51771 https://forge.univention.org/bugzilla/show_bug.cgi?id=44073 https://forge.univention.org/bugzilla/show_bug.cgi?id=43019 https://forge.univention.org/bugzilla/show_bug.cgi?id=55269
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:
Bug Depends on:
Bug Blocks:	57065

Description Arvid Requate

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.