In message <a05200f02ba66778c5b08@[10.0.1.2]>, Brad Knowles writes: >At 8:26 AM +0100 2003/02/05, [EMAIL PROTECTED] wrote:
> My understanding was that a disk is 100% busy, if the heads are >constantly moving to and fro, and there is no period of time when >they aren't being yanked around. In other words, it would be 100% if >there is always at least one outstanding request. Works for me, I'll try if I can instrument that cheaply. > What is your time resolution on this sort of thing? Iostat can >only report in periods as small as one update per second, so I would >hope that you could measure these quantities on a much more frequent >basis, thus being able to make a useful calculation of average values >over that period of time. I currently use binuptime() which means that the resolution is whatever the system provides, which means better than 1 microsecond on all current platforms. The counters are updated in real time, so it's up to you how often you read them. >> For truly trying to understand our disk-I/O load, tracelogs will >> be needed (And I fear they will show a lot of interesting phenomena). > > Hmm. I'd like to learn more about this tracelog concept. Can >you provide any pointers? Well, "tracelog" is simply my word for the concept of recording each and every transaction and run it through some kind of analysis afterwards. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
