Solaris 2.x compat. system accounting, sarcheck for fbsd (commercial)

Narvi narvi at
Fri Apr 11 05:26:11 PDT 2003

On Fri, 11 Apr 2003, Andreas Klemm wrote:

> On Fri, Apr 11, 2003 at 06:01:03PM +1000, Peter Jeremy wrote:
> > On Fri, Apr 11, 2003 at 08:08:23AM +0200, Andreas Klemm wrote:
> > >I wrote some performance monitoring utilities and need for
> > >example a parameter wait for I/O, that I didn't find in our
> > >tools, did I overlook something ?
> >
> > "wait for I/O" is a System-V state that BSD doesn't measure.
> > One of the grey[er] beards may be able to answer why SysV does
> > and BSD doesn't consider "wait for I/O" a state worth measuring.
> Would be interested to hear why, since I think its an interesting
> parameter. At least I know of some sun consultants who are the
> opineon, that this is an important parameter.
> If I understood the parameter right it should bring you a
> value, who measures how often (in percentage) the CPU had
> to wait for I/O operations. Not only disk, additionally
> network I/O as well (from hearsay) but Im not 100% sure about
> it. So theoretically it should bring to you a value, if you
> are I/O bound. Togehter with other values (disk I/O and Network
> stats it should be easy to see, if you have a problem with your
> disks or with your network).

Well, you can get pretty pathetic results where a program causes a
significant amount of time to be spent waiting for I/O and the rest of teh
system crawls. One would hope you just can't get the same situation on

> BTW, are there some automatic tools around for BSD, that
> automate the process of telling you, where you have problems
> with your machine or what kernel parameters need an update ??
> 	Andreas ///
> --
> Andreas Klemm - Powered by FreeBSD 4.7
> Need a magic printfilter today ? ->

More information about the freebsd-hackers mailing list