Bug#522711: [Pkg-xfce-devel] Bug#522711: Bug#522711: xfce4-systemload-plugin: CPU monitor overstates CPU usage

2009-04-10 Thread Yves-Alexis Perez
On ven, 2009-04-10 at 14:06 +0200, Tino Keitel wrote: > > The systemload uses load average (hence the name, I guess). > > No, the corresponding display is called "CPU monitor" in the plugin > settings. The plugin is called systemload. The tooltip on the CPU one is “System load”. End of discussion

Bug#522711: [Pkg-xfce-devel] Bug#522711: Bug#522711: xfce4-systemload-plugin: CPU monitor overstates CPU usage

2009-04-10 Thread Tino Keitel
On Fri, Apr 10, 2009 at 13:01:35 +0200, Yves-Alexis Perez wrote: > On jeu, 2009-04-09 at 19:24 +0200, Tino Keitel wrote: > > > > I also got the impression that the systemload plugin includes the I/O > > wait CPU time into the CPU usage, which is something that most users > > don't expect IMHO. >

Bug#522711: [Pkg-xfce-devel] Bug#522711: Bug#522711: xfce4-systemload-plugin: CPU monitor overstates CPU usage

2009-04-10 Thread Yves-Alexis Perez
On jeu, 2009-04-09 at 19:24 +0200, Tino Keitel wrote: > > I also got the impression that the systemload plugin includes the I/O > wait CPU time into the CPU usage, which is something that most users > don't expect IMHO. The systemload uses load average (hence the name, I guess). Cheers, -- Yves

Bug#522711: [Pkg-xfce-devel] Bug#522711: xfce4-systemload-plugin: CPU monitor overstates CPU usage

2009-04-10 Thread Tino Keitel
On Sun, Apr 05, 2009 at 23:07:25 -0400, Celejar wrote: > Package: xfce4-systemload-plugin > Version: 0.4.2-2 > Severity: normal > > The plugin often reports 100% usage when other system monitors (top, htop, > gnome-system-monitor) show much lower usage (often below 30%). This seems to > occur whe

Bug#522711: xfce4-systemload-plugin: CPU monitor overstates CPU usage

2009-04-05 Thread Celejar
Package: xfce4-systemload-plugin Version: 0.4.2-2 Severity: normal The plugin often reports 100% usage when other system monitors (top, htop, gnome-system-monitor) show much lower usage (often below 30%). This seems to occur when a process that is both disk and CPU intensive, such as a systemwide