Re: deciphering top(1) output
On Feb 11, 2011, at 4:21 PM, Alexander Best wrote: a) my system is 100% idle, since no processes except the idle process takes up up CPU time or b) that a or some processes take up 2% CPU time which aren't being shown or c) that each of my cpu core is only 86.6/89.4% idle? It means (c). Kernel activity, short-lived transient processes, and imperfections in sampling data are the other ~13 / 10 % Regards, -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: deciphering top(1) output
On Fri Feb 11 11, Chuck Swiger wrote:
On Feb 11, 2011, at 4:21 PM, Alexander Best wrote:
a) my system is 100% idle, since no processes except the idle process takes
up
up CPU time or
b) that a or some processes take up 2% CPU time which aren't being shown or
c) that each of my cpu core is only 86.6/89.4% idle?
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:2019: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
PIDUIDTHR PRI NICE SIZERES STATE C TIME WCPU COMMAND
48131 0 1 770 92112K 67164K CPU11 0:02 17.77% cc1
48135 0 1 760 90992K 65712K RUN 0 0:01 15.87% cc1
1001 1 260 1150M 57000K select 1 14:13 7.28% npviewer.bin
2210 1001 2 200 199M 45952K kqread 0 2:38 1.37% chrome
10 0 2 155 ki31 0K32K RUN 0 89:55 1.27% idle
2249 1001 2 200 828M 82864K kqread 1 2:12 0.10% chrome
2247 1001 2 200 846M 84424K kqread 0 0:25 0.10% chrome
48133 0 1 200 13916K 2380K CPU01 0:00 0.10% top
2171 1001 23 200 327M 121M uwait 1 12:11 0.00% chrome
2151 1001 1 200 881M 15400K select 0 6:35 0.00% Xorg
2203 1001 2 200 889M 148M kqread 1 5:07 0.00% chrome
2235 1001 2 200 855M 116M kqread 0 4:51 0.00% chrome
2231 1001 2 200 847M 99464K kqread 0 4:47 0.00% chrome
2208 1001 2 200 853M 103M kqread 0 4:38 0.00% chrome
cheers.
alex
Regards,
--
-Chuck
--
a13x
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: deciphering top(1) output
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 PIDUIDTHR PRI NICE SIZERES STATE C TIME WCPU COMMAND 48131 0 1 770 92112K 67164K CPU11 0:02 17.77% cc1 48135 0 1 760 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 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: deciphering top(1) output
On Fri Feb 11 11, Chuck Swiger wrote: 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 PIDUIDTHR PRI NICE SIZERES STATE C TIME WCPU COMMAND 48131 0 1 770 92112K 67164K CPU11 0:02 17.77% cc1 48135 0 1 760 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 thanks for the hint. in this example however $pid didn't get incremented for over a minute: last pid: 14412; load averages: 0.09, 0.26, 0.29 253 processes: 3 running, 235 sleeping, 15 waiting CPU 0: 12.6% user, 0.0% nice, 7.9% system, 0.4% interrupt, 79.1% idle CPU 1: 13.8% user, 0.0% nice, 5.9% system, 0.0% interrupt, 80.3% idle Mem: 602M Active, 275M Inact, 407M Wired, 8688K Cache, 212M Buf, 669M Free Swap: 18G Total, 910M Used, 17G Free, 4% Inuse, 4K In PID USERNAMETHR PRI NICE SIZERES STATE C TIME WCPU COMMAND 10 root 2 155 ki31 0K32K CPU00 44.7H 198.88% idle 4414 arundel 24 200 334M 93080K uwait 0 34:56 0.00% chrome 4451 arundel 2 200 905M 100M kqread 0 30:12 0.00% chrome 4446 arundel 2 200 836M 53152K kqread 1 28:41 0.00% chrome also i noticed that when a processes CPU activity goes up to let's say 10% and then down again to 0% this doesn't mean that the idle process will jump to 200% instantly, but it takes ~ 10 seconds for it to reclaim the CPU activity that was used by the other process beforehand. cheers. alex Regards, -- -Chuck -- a13x ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: deciphering top(1) output
On Feb 11, 2011, at 5:08 PM, Alexander Best wrote: also i noticed that when a processes CPU activity goes up to let's say 10% and then down again to 0% this doesn't mean that the idle process will jump to 200% instantly, but it takes ~ 10 seconds for it to reclaim the CPU activity that was used by the other process beforehand. WCPU stands for weighted CPU, and is an average over time. Use -C flag if you want raw CPU instead Regards, -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
