From owner-freebsd-hackers@FreeBSD.ORG Mon Aug 4 18:40:17 2014 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4EE62C5A for ; Mon, 4 Aug 2014 18:40:17 +0000 (UTC) Received: from systemdatarecorder.org (mail.systemdatarecorder.org [54.246.96.61]) (using TLSv1.1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client CN "localhost", Issuer "localhost" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id DC7A527FB for ; Mon, 4 Aug 2014 18:40:16 +0000 (UTC) Received: from nereid (84-253-211-213.bb.dnainternet.fi [84.253.211.213]) (authenticated bits=0) by systemdatarecorder.org (8.14.4/8.14.4/Debian-2ubuntu2.1) with ESMTP id s74IbcHj029820 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 4 Aug 2014 18:37:38 GMT Date: Mon, 4 Aug 2014 21:39:48 +0300 From: Stefan Parvu To: David Wolfskill 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> Organization: systemdatarecorder.org X-Mailer: Sylpheed 3.4.2 (GTK+ 2.24.22; amd64-portbld-freebsd11.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Aug 2014 18:40:17 -0000 > 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