I am not sure that's really true. ALL
writes are going to be "sequential" if they can - the filer writes
to NVRAM not disk directly. So the AFAIK the writes are always as
sequential as they can be*
Reads are cached like crazy, esp when PAM/FlashCache etc.
*Generally when someone says they want to know they are looking
for bottlenecks. I stand by statit as a tool for this since you
are seeing how each disk is working. You might not know exactly
what's causing the issue but it's good data to know what is going
on at the aggregate level (which is what he is asking about) and
the RG level (which is where the performance for an aggregate is
going to be determined).
Disk Statistics (per second)
ut% is the percent of time the disk was busy.
xfers is the number of data-transfer commands issued per
second.
xfers = ureads + writes + cpreads + greads + gwrites
chain is the average number of 4K blocks per command.
usecs is the average disk round-trip time per 4K block.
Jeremy Page |
Senior Technical Architect | Gilbarco Veeder-Root, A
Danaher Company
Office:336-547-5399 | Cell:336-601-7274 | 24x7
Emergency:336-430-8151
On 01/16/2014 04:56 PM, Jeff Mohler wrote: