In the last episode (Apr 16), Poul-Henning Kamp said: > In message <42616D77.2070205_at_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_at_allantgroup.comReceived on Sat Apr 16 2005 - 19:45:49 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:32 UTC