Wakes processor way to often than needed

Bug #506884 reported by Linard Verstraete on 2010-01-13
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
xfce4-systemload-plugin
Invalid
Undecided
Unassigned
xfce4-systemload-plugin (Ubuntu)
Undecided
Unassigned

Bug Description

Binary package hint: xfce4-systemload-plugin

Ubuntu has set the goal for mobile devices to last longer on a single battery charge. This can be done by several things, of which keeping the amount of wakening the processor to a minimum. Tickless-kernels was a great move forward and now they advice to have around 50 interrupts per second for a fully but idle desktop.

xfce4-systemload-plugin 1:0.4.2-1ubuntu3, which has been released for hardy and intrepid, did 4 interrupts per second. This gives the user every 250 milliseconds an update of the systems load. This is a reasonable value for something that has to present non-crucial and more or less real-time info.

xfce4-systemload-plugin 1:0.4.2-3ubuntu1, which has been released for karmic and lucid, is doing 12 interrupts per second. This makes it almost the second top-cause for wakening the processor after the kernels function itself. It also takes as much as a quarter of the "allowed" 50 interrupts. Giving this non-crucial info every 85 milliseconds is not reasonable since the user will not gain any informative info. If you program gets stuck and your processor goes up to 100% load, you'll notice this in the same way on a 250 millisecond update as on a 85 millisecond update. I think this is just unnecessary usage of processor-cycles and power.

Possible solutions:
1) Set the value back to a 4Hz update, like it has been.
2) Provide a simple option to let the user chose the update frequency, like already done in the xfce4-sensors-plugin.

summary: - Wakes processor why to often than needed
+ Wakes processor way to often than needed
tags: added: iso-testing
Charlie Kravetz (charlie-tca) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/Xfce. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance.

Changed in xfce4-systemload-plugin:
status: New → Incomplete
Changed in xfce4-systemload-plugin (Ubuntu):
status: New → Incomplete
Launchpad Janitor (janitor) wrote :

[Expired for xfce4-systemload-plugin (Ubuntu) because there has been no activity for 60 days.]

Changed in xfce4-systemload-plugin (Ubuntu):
status: Incomplete → Expired
Charlie Kravetz (charlie-tca) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in xfce4-systemload-plugin:
status: Incomplete → Invalid
Changed in xfce4-systemload-plugin (Ubuntu):
status: Expired → Invalid
Linard Verstraete (linardv) wrote :

I can not reproduce the bug anymore in an fully updated Lucid installation. Neither could I find something in the source code of the plug-in that would explain the described behavior of this bug. So bug closed, also from my point of view.

tags: removed: iso-testing
tags: added: iso-testing
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers