Yuri wrote: > Look below: load over 7 and no processes take much CPU. > > Yuri > > 7.2-PRERELEASE, 32-bit on i7-920. > > ------------------------------------------------------------ > last pid: 93192; load averages: 7.68, 6.27, > 4.61 > > up 2+03:11:29 20:25:24 > 204 processes: 9 running, 193 sleeping, 1 stopped, 1 zombie > CPU: 5.3% user, 0.0% nice, 0.0% system, 0.0% interrupt, 94.7% idle > Mem: 867M Active, 1684M Inact, 279M Wired, 65M Cache, 112M Buf, 92M Free > Swap: 16G Total, 142M Used, 16G Free
Couple of possible reasons: 1) You have many short lived processes that are spawned, do some work and die (some kind of web server?). You can't see them because they live too shortly. See if the "last pid" is rapidly increasing. Also, hit "H" to display individual threads. 2) You have kernel processes that are doing some intermittent work. Hit "S" to see them. In any case, see the line where it says "9 running" processes? This is where the load average comes from. The CPU utilization is not directly related to the load average. Load average is not scaled to NCPU - a count of "7" (or in your case, aymptotically 9) means there are 7 (or 9) processes wanting to run. The "global" CPU utilization (the "CPU:" line) *is* scaled to NCPU - 100% here means all CPUs are busy all the time. Individual processes' CPU utilization *isn't* scaled to NCPU. A process taking 100% CPU on its own means it only requires / runs on 1 CPU. A multithreading process can have, for example, 400% CPU utilization and the global CPU utilization can be <= 100%.
signature.asc
Description: OpenPGP digital signature
