On Thu, 14 Sep 2006, Dan Nelson wrote:
In the last episode (Sep 14), Ian Smith said:
[..]
However that doesn't explain this typical top view when the system is
quiescent or nearly so, as it mostly is, with only 5-minutely crons and
11-minutely entropy runs and the odd sendmail to be
In the last episode (Sep 15), Ian Smith said:
On Thu, 14 Sep 2006, Dan Nelson wrote:
I would guess that maybe xmms (or some other threaded app) is your
hidden CPU consumer. The kernel does not calculate %CPU correctly
for libkse-threaded programs, and they usually show up as 0% all
On Thu, 14 Sep 2006, Giorgos Keramidas wrote:
On 2006-09-14 00:48, Tamouh H. [EMAIL PROTECTED] wrote:
I think TOP and load averages are no longer accurate on FBSD 5.x and
6.x with SMP kernel. As far as I've seen. Load averages hit sometimes
8.0 without a noticable degradation in
In the last episode (Sep 14), Ian Smith said:
I still can't fathom what top tells me on a UP 5.5-STABLE system (300MHz
Celeron if speed's relevant). I initiated this thread (weeks ago :) re
seeing 0.0% idle (as expected) during buildworld but not seeing anything
add up to anything like 100%,
In recent 6.X versions, you can use 'S' to show system threads too.
For an even more fine-grained view, you can use 'H' to show
each thread separately.
Then there is also the 'CPU' mode (as opposed to the default 'WCPU'
mode of top).
I've the same issue with FBSD 5.4 and TOP. In
In the last episode (Sep 14), Tamouh H. said:
This is one TOP that freaked me out, notice Idle CPU is 70% while the
process is showing it is using 99% of CPU. systat draws more accurate
picture, however, load average is still useless as far as performance
monitoring :
last pid: 10174; load
On 2006-09-14 00:48, Tamouh H. [EMAIL PROTECTED] wrote:
I think TOP and load averages are no longer accurate on FBSD 5.x and
6.x with SMP kernel. As far as I've seen. Load averages hit sometimes
8.0 without a noticable degradation in performance.
This is one TOP that freaked me out, notice
Ian Smith wrote:
But since running 5.x (5.5-STABLE since 1st Aug) top can show 0.0% idle
but the cpu usages shown don't add up to much of a fraction of 100%.
[ ... ]
Any ideas why top hasn't much of a clue about what's consuming cpu?
Sure, if you're running a parallel make, that will be
On Thu, 10 Aug 2006, Chuck Swiger wrote:
Ian Smith wrote:
But since running 5.x (5.5-STABLE since 1st Aug) top can show 0.0% idle
but the cpu usages shown don't add up to much of a fraction of 100%.
[ ... ]
Any ideas why top hasn't much of a clue about what's consuming cpu?
In the past (FreeBSD 2.2, 3.3, 4.5 through 4.10) if I noticed unexpected
high cpu use, say on xload or ascpu, I'd just run top to determine what
the pig was, and kill it if something (usually netscape :) was wedged.
But since running 5.x (5.5-STABLE since 1st Aug) top can show 0.0% idle
but the
But since running 5.x (5.5-STABLE since 1st Aug) top can show
0.0% idle but the cpu usages shown don't add up to much of a
fraction of 100%.
For a typical illustration: 'make index' has been running for
hours, and here's a shot of 'nice top', o)rdered by cpu,
showing S)ystem procs:
On 2006-08-10 00:45, Tamouh H. [EMAIL PROTECTED] wrote:
But since running 5.x (5.5-STABLE since 1st Aug) top can show
0.0% idle but the cpu usages shown don't add up to much of a
fraction of 100%.
In recent 6.X versions, you can use 'S' to show system threads too.
For an even more
12 matches
Mail list logo
