Univention Bugzilla – Full Text Bug Listing |
Summary: | Firefox takes high CPU consumption during appliance setup on local machine | ||
---|---|---|---|
Product: | UCS | Reporter: | Alexander Kläser <klaeser> |
Component: | System setup | Assignee: | UCS maintainers <ucs-maintainers> |
Status: | RESOLVED WONTFIX | QA Contact: | |
Severity: | normal | ||
Priority: | P5 | CC: | gulden |
Version: | UCS 4.0 | ||
Target Milestone: | UCS 4.0-x | ||
Hardware: | Other | ||
OS: | Linux | ||
See Also: |
https://bugzilla.mozilla.org/show_bug.cgi?id=508427 https://forge.univention.org/bugzilla/show_bug.cgi?id=40985 |
||
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): | UCS Performance | |
Max CVSS v3 score: |
Description
Alexander Kläser
2015-07-09 11:56:27 CEST
There seems to be a workaround (https://bugzilla.mozilla.org/show_bug.cgi?id=508427#c131) for lowering the CPU load: ---------- 8< ---------- [...] A little hunting around layout/base/nsRefreshDriver.cpp in the source code to firefox and I found "layout.frame_rate" which defaults to 60 frames/second (if set to -1 in the about:config page). If in about.config I set layout.frame_rate to 10 then I would get about 10 wake ups per second. [ I am counting a wakup as a whole cycle of those poll()s, recvfrom()s and a read("\372") that you see in strace. ] Set layout.frame_rate to 3 and you get 3 wakeup/sec. With lower rate settings I get very slow/laggy UI responsiveness (for things like typing a new URI in the URI bar). A rate of 15 is pretty usable, though, and yields about 4X less aggressive wake ups/second -- which for laptop battery people may be helpful. So, at least on my system and I suspect others this seems to be a the "knob" to control the effect. It also may answer some questions raised earlier about "which timer thread" and so forth. [...] ---------- 8< ---------- This issue has been filled against UCS 4.0. The maintenance with bug and security fixes for UCS 4.0 has ended on 31st of May 2016. Customers still on UCS 4.0 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. |