Date: Fri, 11 Feb 2011 16:44:40 -0800 From: Chuck Swiger <cswiger@mac.com> To: Alexander Best <arundel@freebsd.org> Cc: freebsd-questions@freebsd.org Subject: Re: deciphering top(1) output Message-ID: <2325F972-050A-4CA2-9900-27000776E52A@mac.com> In-Reply-To: <20110212004100.GA98882@freebsd.org> References: <20110212002129.GA95360@freebsd.org> <2F104DA0-9420-4E7A-9023-A7C6AC5EC173@mac.com> <20110212004100.GA98882@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2325F972-050A-4CA2-9900-27000776E52A>