Univention Bugzilla – Bug 48228
Loading multiple LDAP objects (>1000) takes too long
Last modified: 2022-11-09 20:38:22 CET
From the usability point of view, loading multiple LDAP objects (>1000) takes too long. On a productive system I just had at hand, for example, 35 seconds. This is of course too long because 1000 objects are quickly reached when loading only one school. Furthermore, a search limit ("The requested search returned too many results ...") is not accepted in modern environments. Paging in the web environment is used for this purpose. Normally already from 100 users. Possibly related bugs: http://forge.univention.org/bugzilla/show_bug.cgi?id=44422 <font color="#ffff00">http://forge.univention.org/bugzilla/show_bug.cgi?id=44870
In a short test it took here 3.5 seconds to open a user list with about 1.000 users. So I guess there is something more specific in the environment. Can you append log files for UMC / UDM with debug level 4? And maybe you can also set LDAP debug to stats so that we can see which searches took so long. It is also possible than some attribute is not in the index. Maybe the LDAP ACLs are the problem? Did you search as Administrator? If it is a problem for the customer, you can also create a support ticket.
This issue has been filed against the UCS version "unstable" which does not really exist. Please change the version value.
Performance depends stringly on the ACLs traversed. Tests must be done with both cn=admin and non-cn=admin accounts (in school context teacher account).
In UCS@school we just reduced the loading time of a UMC module massively by using direct LDAP lookups and not using UDM: Bug #47885.