Bug 43765 - LMDB listener code could reduce storage required for DNs in dntree
LMDB listener code could reduce storage required for DNs in dntree
Product: UCS
Classification: Unclassified
Component: Listener (univention-directory-listener)
UCS 4.2
Other Linux
: P5 enhancement (vote)
: ---
Assigned To: UCS maintainers
UCS maintainers
Depends on: 23367
  Show dependency treegraph
Reported: 2017-03-09 12:54 CET by Arvid Requate
Modified: 2020-07-03 20:54 CEST (History)
6 users (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):
Max CVSS v3 score:
requate: Patch_Available+

cache_rdn.patch (5.67 KB, patch)
2017-03-09 12:54 CET, Arvid Requate
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Arvid Requate univentionstaff 2017-03-09 12:54:23 CET
Created attachment 8511 [details]

The LMDB listener code could reduce storage required for DNs in dntree. In my experiments with 1k users (create-32k-users-in-groups -n 1024) the attached patch reduced the cache size by about 1.5 percent. So it's a very small feature.

In a quick test I had the impression that this patch also works with cache data generated by the initial LMDB listener cache_dn.c code. I'm using the (largely undocumented) ldap_str2rdn function, which makes this possible as a side effect.

+++ This bug was initially created as a clone of Bug #23367 +++
Comment 1 Ingo Steuwer univentionstaff 2020-07-03 20:54:58 CEST
This issue has been filed against UCS 4.2.

UCS 4.2 is out of maintenance and many UCS components have changed in later releases. Thus, this issue is now being closed.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen it and update the UCS version. In this case please provide detailed information on how this issue is affecting you.