Comment 2 for bug 1871008
Revision history for this message
| Christoph Anton Mitterer (calestyo) wrote | #2 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
Hey.
Sorry for the delay in replying, but noticing the energy consumption of diodon was actually just a side product of me trying to trace down some much more serious problems with CPU temperature increase ([0] and [1]).
I've had tried clearing the history, but I don't think this changes anything.
Right now I've just did a fresh start of diodon with debug output, and even though it's not active (i.e. the menu of it) and I do not mark/select/copy anything, top shows:
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
6314 calestyo 20 0 649468 28616 20120 S 0,3 0,1 0:01.00 diodon
The CPU utilisation actually varies, sometimes it's 0%... but it also goes up to 0,7%... but usually it's 0,3%.
If I do mark/select something it will go up noticeably... like 6-8% usage.
But even when doing nothing, not even moving the mouse pointer or typing anything it's always around 0,3%
Looking at it from powertop (again, when I don't use it or select something or so):
Power est. Usage Events/s Category Description
...
110 mW 3,1 ms/s 27,4 Process [PID 6314] diodon
...
It's always around 100-115 mW.
Attached is also the log as you wanted.
Cheers,
Chris.
[0] https:/
[1] https:/