Univention Bugzilla – Full Text Bug Listing |
Summary: | Performance optimization for App Center: UCR | ||
---|---|---|---|
Product: | UCS | Reporter: | Dirk Wiesenthal <wiesenthal> |
Component: | App Center | Assignee: | Dirk Wiesenthal <wiesenthal> |
Status: | CLOSED FIXED | QA Contact: | Florian Best <best> |
Severity: | normal | ||
Priority: | P5 | CC: | best, damrose, gohmann, klaeser, walkenhorst |
Version: | UCS 4.1 | ||
Target Milestone: | UCS 4.1-0-errata | ||
Hardware: | Other | ||
OS: | Linux | ||
What kind of report is it?: | --- | 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: | |||
Bug Depends on: | |||
Bug Blocks: | 38545 |
Description
Dirk Wiesenthal
2015-12-14 00:06:24 CET
Fixed in univention-appcenter 5.0.19-28.86.201512140023 (In reply to Dirk Wiesenthal from comment #0) > One way might be caching of UCR. Currently, UCR is initialized in a lot of > local functions. This way one does not have to think about thread safety, > concurrent processes and so on. But it may cost too much time. Do you have any indications that UCR variable loading is a bottle neck w.r.t. performance? Before patch: time umc-command appcenter/query -U Administrator -P univention real 0m10.883s user 0m0.280s sys 0m0.036s After patch: (no pickle files yet) time umc-command appcenter/query -U Administrator -P univention real 0m5.629s user 0m0.272s sys 0m0.036s ucr is still a argument of get_app_ldap_object(): python/appcenter/udm.py:def get_app_ldap_object(app, lo=None, pos=None, ucr=None, or_create=False): Yes, left it there for backwards compatibility, but I guess this is silly (as I changed ApplicationLDAPObject, too). univention-appcenter 5.0.19-38.95.201601050043 OK |