Author: Linchi SheaLinchi Shea Date: Jul 1, 2008 12:25
> in one IO. and I think the higher MB/IO will be better. is that a good
> reasoning, or am I missing something?
Not really. Block size per I/O is something you can control with sqlio or
something an app has control when issuing I/Os. It's more like an 'input
parameter' than an 'output value'. The key measures of an I/O subsystem's
performance are: (1)Megabytes per second--how much data can you push through
the I/O pipeline, (2) I/Os per second--how many I/Os can you do, and (3) I/O
response time (aka latency)--how fast can you do an I/O.
> regards to Outstanding IOs, is it identical to the disk queue lenght? if
It >can< be identical to the disk queue length. But since there may be
multiple layers of queues and some queues may not be directly visible to the
OS perfmon counter, it may not be identical to what the perfmon counter
measures. But in the case of sqlio, you should see the same value with
PhysicalDisk\current queue length for teh drive.
Linchi
"light_wt" wrote:
> Linchi,
>
> thanks for your insight. Yup, the block size is the only difference between
> the two.
>
> reason i ask is because, if one diviide the MBs/sec by IOs/sec, i will get
> MB/IO. another...
|