Gnome System Monitor: Swatting bugs 4

Earlier this year I took over maintainership of Gnome System Monitor. It had been neglected for a couple years which was obvious by taking a look at the bugs piling up in Bugzilla. When I started there were about 255 bugs which I quickly got down to just under 200.

Up until a few weeks ago it had stayed at that level. But a few weeks back Robert Roth appeared out of nowhere and started triaging bugs and submitting new patches and updating old patches. He’s been keeping me busy reviewing and applying patches. With his help the bug count is now at 146. Still high but very good progress. So, thanks Robert!

The big new feature so far this cycle is Control Groups support. Jason Baron from Red Hat has added an option to view the control group information for each process. This is a work in progress. I’ve included an early patch in the 3.3.2.1 release. If you find bugs or just want to follow the progress please visit bug #663644. Also, thanks to Lennart for his input on how best to implement this.

With many bugs squashed and a few new features, the 3.4 release stands to be The best release ever (TM).

4 thoughts on “Gnome System Monitor: Swatting bugs

  1. Reply fabiand Nov 24, 2011 01:36

    Very nice too see cgroup support land in gsm :) congrats.

  2. Reply jeff Nov 24, 2011 06:31

    This is great! I’m happy to hear that you picked up maintainership of g-s-m, it is much needed. My biggest annoyance is the terrible CPU usage (that probably stems from drawing the graphs). Have you looked into https://github.com/chergert/uber-graph by any chance?

  3. Reply Chris Nov 25, 2011 02:27

    @jeff: Yes, I’m very aware of this problem. Bug #636343 is also requesting to use uber-graph. Feel free to start a discussion or submit a patch there.

    Cheers,
    Chris

  4. Reply Robert Roth Jan 8, 2012 09:21

    @Chris, jeff: I’m afraid not the graph drawing is consuming CPU, but updating the process list. A simple experiment to check this: open top to monitor System monitor CPU usage (kindoff funny :) ), and change the processes to view from All processes to My processes then to Active processes. As the active processes list contains less processes than My processes, GSM consumes less CPU when set to show only active processes.

    But this is only my guess, please mention any evidence you have to prove that the resource-consuming stuff is the graph drawing.

Leave a Reply