deciphering top(1) output
Chuck Swiger
cswiger at mac.com
Sat Feb 12 00:44:52 UTC 2011
On Feb 11, 2011, at 4:41 PM, Alexander Best wrote:
>> It means (c). Kernel activity, short-lived transient processes, and imperfections in sampling data are the other ~13 / 10 %....
>
> thanks. it seems in some cases these imperfections have quite an impact:
>
> last pid: 48135; load averages: 5.11, 5.38, 5.02 up 0+03:15:20 19:31:52
> 271 processes: 15 running, 242 sleeping, 14 waiting
> CPU 0: 76.4% user, 0.0% nice, 21.7% system, 2.0% interrupt, 0.0% idle
> CPU 1: 85.0% user, 0.0% nice, 12.6% system, 2.4% interrupt, 0.0% idle
> Mem: 1078M Active, 334M Inact, 403M Wired, 79M Cache, 212M Buf, 68M Free
> Swap: 18G Total, 438M Used, 18G Free, 2% Inuse
>
> PID UID THR PRI NICE SIZE RES STATE C TIME WCPU COMMAND
> 48131 0 1 77 0 92112K 67164K CPU1 1 0:02 17.77% cc1
> 48135 0 1 76 0 90992K 65712K RUN 0 0:01 15.87% cc1
Sure. Compiling software is a classic example where lots and lots of CPU intensive, short-lived processes are started. Pay attention to last pid field; if it is steadily growing, especially at a rapid rate, lots of processes are spawning....
Regards,
--
-Chuck
More information about the freebsd-questions
mailing list