Why is gnome-system-monitor's performance seemingly so lousy?

Asked by Eric P. Mangold on 2009-03-09

When I launch gnome-system-monitor by clicking on the System Monitor tray-cpu-graph it takes about 4-5 seconds to load up and then consumes between 15% to 55% CPU, with it usually hovering above 33%. However after letting it run for several minutes the CPU usage pegs out above 85% (this may be a separate issue).

Compare this to Sysinternal's Process Explorer (under Windows on the same machine) which runs at between 1.5% to 3.0% when updating its process list every second, sorted by CPU usage while drawing 3 small graphs. And it loads much, much faster.

As a user and developer this strikes me as heavy and bloated, and for an app that I like to refer to quite often it's really annoying.

Sorry that all I have to contribute is a complaint... I hope this information is at least deemed useful by someone.

I have not changed any of the update intervals from the detault. They are:

Process update interval (main window): 3.0 seconds
Graphs update interval: 1.0 seconds
Filesystem updates interval: 5.0 seconds

gnome-system-monitor version 2.24.1

Question information

English Edit question
Ubuntu gnome-system-monitor Edit question
No assignee Edit question
Last query:
Last reply:
Shyam (shyam.s) said : #1


You can find out process that uses CPU resource more through a command "top". Open a terminal and give "top". You'll come to know which process uses more CPU.


Eric P. Mangold (teratorn) said : #2

Sorry, but my question is about gnome-system-monitor itself, not processes in general.

Shyam (shyam.s) said : #3

yes, I could very well understand your problem, but the reason why I suggested the top command is to identify which process utilizes more cpu, since gnome-system-monitor doesn't use that much of resources.....


Seems related to this fixed bug https://bugs.edge.launchpad.net/bugs/187383

Hope this helps

Can you help with this problem?

Provide an answer of your own, or ask Eric P. Mangold for more information if necessary.

To post a message you must log in.