Date: Mon, 4 Aug 2014 21:39:48 +0300 From: Stefan Parvu <sparvu@systemdatarecorder.org> To: David Wolfskill <david@catwhisker.org> Cc: freebsd-hackers@freebsd.org Subject: Re: cpu utilization break down via sysctl Message-ID: <20140804213948.4d1d2eb86b59e4a7e28c838b@systemdatarecorder.org> In-Reply-To: <20140804165350.GQ1228@albert.catwhisker.org> References: <20140804190923.95fec6a00d175ffee89c4af5@systemdatarecorder.org> <20140804162056.GP1228@albert.catwhisker.org> <20140804194036.be325ee5822bbcb2623db358@systemdatarecorder.org> <20140804165350.GQ1228@albert.catwhisker.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> Err... Well... Maybe? The numeric values are the values of the counters > at the time the information was acquired. > > I'd probably depict them more as: > > user nice system intr idle > cpu0: 28845 2060 22253 1805 1197920 > cpu1: 27677 1477 22399 2109 1199180 > cpu2: 32342 1649 19499 894 1198458 > cpu3: 29670 1678 20324 1471 1199699 right. > If you mean total non-idle CPU, yes. For determining available CPU, you > need to include idle. > super. Many thanks again. I will put together these and post my progress. I will do first the CPU utilization, then go to mem, disk and network io utilizations. I need as well the get the run-queue length, load average seems very simple. Not sure how hairy things will get on those parts when I will need per disk or per NIC throughput iops or read KB/sec. One thing at the time. Cheers, -- Stefan Parvu <sparvu@systemdatarecorder.org>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20140804213948.4d1d2eb86b59e4a7e28c838b>