Version: 1.2.0 (using KDE KDE 3.5.5) Installed from: SuSE RPMs OS: Linux Situation: My fan goes off cause the CPU load shoots up to 100% Reaction: First look at KSysGuard-Applet in the controlbar Frustration: It does not show me the culprit I'd love to have a fast and obvious place showing me, which process eats up all CPU! It just takes too long to open up the processtable, deactivate the treeview, sort for CPU-Usage, pic the process, activate the treeview again, sort alphabetically and scroll to monitor it. Most obvious would be the small graph integrated in Kicker or the tooltip for it. I emphasize: It must be fast. This is not the usual whining about my computer being so slow. In presence of an outrageous process, it just takes to long to open up any but the simplest dialogs. Thats not the time for graphic eye candy. Possiple implementation: a) A new sensor, that can be added to the view, displaying a single line of text with the most active process b) An empty sensor, that only affects the tooltip in combination with Bug 59052, so that the name of the fake-sensor in the tooltip is the process. c) A ballon popup d) A new entry in the right-click menue, that shows the process. e) A global keyboard shortcut, maybe attach to Ctrl+Alt+Delete session management. There are more advanced features related to this: 1. Offer a way to send a signal to that process (would be easiest through the right-click menu) 2. Keep a history attached to the CPU-consumption-diagram, so that peeks of the past can be analyzed and related to now sleeping or finished programs. This could be done with a tooltip sensitive to the mouse x-Position or if the displaying line tracks the mouse. 3. Save not only the process, but the full path in the tree like "ZMD : update-status"
Hi, This is mostly implemented now. In KDE4, pressing ctrl+esc shows the process table pretty much instantly. The process using all the cpu is shown at the top. However it would indeed be useful to show the process that is using all the cpu in the tooltip.
Don't we first sort by username, then cpu usage?
(In reply to comment #2) > Don't we first sort by username, then cpu usage? Yes, but if you sort by CPU usage, it remembers that change. Closing this now since it's 'fixed' in ksysguard 4 and we don't have a kicker applet in kde4.