February 2010 (1)
September 2009 (1)
May 2009 (1)
April 2009 (1)
March 2009 (4)
January 2009 (3)
November 2008 (2)
October 2008 (2)
September 2008 (1)
August 2008 (5)
July 2008 (3)
June 2008 (1)
May 2008 (5)
April 2008 (8)
March 2008 (3)
February 2008 (1)
January 2008 (2)
December 2007 (2)
November 2007 (4)
October 2007 (17)
September 2007 (9)
2008-04-10 09:10:56
In the whole time I’ve been a Gnome user, which would be several years now, I don’t think I’ve ever seen gnome-system-monitor use less then 5% CPU on average.
I have a honking fast box with lots of RAM here, and gnome-system-monitor still registers on its own display. Contrast this with the humble top, which rarely uses more than 1%.
It seems to me that when you actually want a system monitor is when your system is under heavy load. In which case the last thing I want to do is fire up a new app that materially adds to the problem.
From Brenda on 2008-04-11 09:24:57
try wmtop.From stephen on 2008-04-11 10:46:02
I’m pretty sure it’s the load of redrawing the screen. Reducing the refresh period drops the load markedly.
I’m also suspecting that g-s-m and top aren’t using quite the same metric to measure cpu.
Another thing to poke into on the weekend, I’m interested now.
Rendered at 2010-08-01 22:29:02
From Jason Pollock on 2008-04-10 10:07:20
We had a CPU monitor as part of our product. It had a bug that was rather difficult to track down, that kept it at the top of the CPU usage. The problem was, when it went to ask the kernel which processes had consumed CPU recently, it was always the most recent, and therefore at the top of the stats. To get a more accurate measurement (reflecting top or sar for example), we had to start monitoring, put the process to sleep for a couple of seconds and then check the results.
I wouldn’t be surprised if the gnome app had the same problem we did.