Bug 39777

Summary: Improve speed of opening UDM objects in the frontend
Product: UCS Reporter: Alexander Kläser <klaeser>
Component: UMC - Domain management (Generic)Assignee: UMC maintainers <umc-maintainers>
Status: CLOSED WONTFIX QA Contact:
Severity: normal    
Priority: P5 CC: best, dormann, gohmann, klaeser
Version: UCS 4.1   
Target Milestone: UCS 4.1-x   
Hardware: Other   
OS: Linux   
What kind of report is it?: Bug Report What type of bug is this?: 5: Major Usability: Impairs usability in key scenarios
Who will be affected by this bug?: 4: Will affect most installed domains How will those affected feel about the bug?: 2: A Pain – users won’t like this once they notice it
User Pain: 0.229 Enterprise Customer affected?:
School Customer affected?: ISV affected?:
Waiting Support: Flags outvoted (downgraded) after PO Review:
Ticket number: Bug group (optional): UCS Performance, Usability
Max CVSS v3 score:
Bug Depends on: 38190    
Bug Blocks:    

Description Alexander Kläser univentionstaff 2015-11-04 14:55:14 CET 
The speed improvement for Bug 38190 could be done for other object types, as well. This would be easy for UDM modules with only one object type (e.g., groups) and would be harder to do for UDM modules with several types (e.g., computers).

+++ This bug was initially created as a clone of Bug #38190 +++

If I open a user on demo.univention.de, it took between 2 to 4 seconds. A user should be opened in less than a second.
Comment 1 Florian Best univentionstaff 2017-10-12 19:26:19 CEST 
Happened to me again: I have 2000 users and do a simple "udm users/user list" which takes 50 seconds on a DC Slave and 20 seconds on a DC Master. On the DC Master the ldap search for all user objects takes 3,7 seconds. If no obj.open() call is done it takes 6,7 seconds.
Comment 2 Stefan Gohmann univentionstaff 2019-01-03 07:19:01 CET 
This issue has been filled against UCS 4.1. The maintenance with bug and security fixes for UCS 4.1 has ended on 5st of April 2018.

Customers still on UCS 4.1 are encouraged to update to UCS 4.3. Please contact
your partner or Univention for any questions.

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