Date: Sat, 16 Apr 2005 16:45:47 -0500 From: Dan Nelson <dnelson@allantgroup.com> To: Poul-Henning Kamp <phk@phk.freebsd.dk> Cc: Eric Anderson <anderson@centtech.com> Subject: Re: gstat shows > 100% busy Message-ID: <20050416214547.GS4842@dan.emsphone.com> In-Reply-To: <4281.1113685517@critter.freebsd.dk> References: <42616D77.2070205@centtech.com> <4281.1113685517@critter.freebsd.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
In the last episode (Apr 16), Poul-Henning Kamp said: > In message <42616D77.2070205@centtech.com>, Eric Anderson writes: > >> The "ms/r" and "ms/w" give you the time it takes to send a > >> transaction through (in milliseconds, for read and write > >> respectively) and those are the numbers you should monitor. > > These on the other hand are what people really care about: how fast > (or slow) will it be to access the disk. If you run a disk benchmark > you will notice that the service time has seismographic sensitivity, > run a stupid access pattern and it explodes into the 100s of > milliseconds. > > >Is there a place to grab those stats in a more 'script friendly' > >way? I am the author of a (rather cheesy) tool called bsdsar, and > >I'm thinking about updating it with all the new cool 5.X-isms. > > Go for it. There is a pretty simple API to pull it out of the > kernel, check the gstat source. Also see the devstat manpage and the source to iostat. -- Dan Nelson dnelson@allantgroup.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050416214547.GS4842>