top does __NOT__ explain the loadavg (if it did, I would not have complained): non-0 CPU users account to 10-15% at most. (this, however, is absurd in itself! why does compiz take 3-4% of CPU on a 2.7GHz system when twm/fvwm/gwm/scwm never took more than 1% on a 200MHz system?!)
moreover, top __CANNOT__ always explain loadavg. (e.g., `ls /mnt/foo` will be at 1 loadavg if /mnt/foo is NFS-mounted and the server is down). "The load average code runs in the heart of the kernel, and it doesn't know anything other than if a CPU is in use or not busy at the 5 second sample time." first of all, loadavg is not about CPU: "the number of processes in the system run queue averaged over various periods of time." there should be a way to get __WHICH__ processes occupied the the system run queue, in addition to _how many_ of them. otherwise this loadavg metric is next to useless to the users, even if the developers are convinced that it is "correct" in some way. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/985661 Title: High load average To manage notifications about this bug go to: https://bugs.launchpad.net/xubuntu-desktop/+bug/985661/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
