kde and gnome system monitors giving different results. I this case I was just backing up some virtualbox VDIs. Do not think the cpu was maxed out as the KDE sys monitor was showing…any ideas why this would happen?
http://img.photobucket.com/albums/v469/mejason69/Screen%20Shots/sysmonitorlies.png
Odd.
If you run
top
from a terminal it will show what is happening.
I don’t thrust those things, and certainly not the one from Gnome.
KDE seems fine but as soon as you run the gnome system monitor on the same machine you’ll see that it constantly takes arround 30 to 35% CPU cycles.
As soon as you close the gnome system monitor it reverts back to values between 2 and 6%.
I have a monitor in my cairo-dock and this one gives correct values at all times.
I think it was the gnome monitor that was telling the “truth”. No way my system was using 100% cpu to copy files to an external drive. Hell I have a 3.2ghz Core 2 duo.
@caf4926 - I use top all the time… esp since almost all my servers are cli only.
Maybe one is showing 1 core, the other two?
In KDE3 system monitor (the one in the system tray) copying do show 100% usage, but of I/O cycles, not CPU cycles. The CPU use is quite low.
Just guessing…