Date: Tue, 23 Sep 2014 10:45:14 +0200 From: Borja Marcos <borjam@sarenet.es> To: Stefan Parvu <sparvu@systemdatarecorder.org> Cc: freebsd-performance@freebsd.org Subject: Re: I like iostat, but... Message-ID: <659899B2-1816-41FA-9DED-57416928A1EE@sarenet.es> In-Reply-To: <20140923113844.6f9e9584965dfd401f6943af@systemdatarecorder.org> References: <20140922212209.GA9619@albert.catwhisker.org> <20140923113844.6f9e9584965dfd401f6943af@systemdatarecorder.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sep 23, 2014, at 10:38 AM, Stefan Parvu wrote: >=20 >> ... I rather wish I could get the same information via sysctl. = (Well, >> something seems to be available via the "opaque" kern.devstat.all >> sysctl(8) variable, but sysctl(8) doesn't display all of it, and = parsing >> it seems as if that would require knowledge about the internals of = the >> system where the data were acquired.) >=20 > I gave up parsing sysctl via Perl for disks and network devices. It = would be > nice to have devstat properly working via sysctl for disk devices. = Similar way > kern.cp_times does. Currently there is no simple way to extract per = disk stats from > sysctl as a Perl or Sh consumer, unless we build a C module to do = that.=20 Anyway, for disk stats GEOM offers a nice API. You can get delays per = GEOM provider, bandwidths, etc. Borja.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?659899B2-1816-41FA-9DED-57416928A1EE>