Any feedback on this will be highly appreciated.
1.-t flag(Threads) – If I capture worker thread information using this query
SELECT SUM(current_workers_count) as [Current worker thread] FROM sys.dm_os_schedulers
and then calculate the average number of threads from this data and use this as the reference point for –t value scaling upto 256 while testing SQLIO - would this be a right approach for determining right number of threads ?
2.Do the below Perfmon counters map upto to SQLIO numbers as follows : ?
i - (Disk Reads / Second & Disk Writes / Second) --> IOPS,
ii- (Average Disk sec / read & Average Disk sec / write) --> Latency,
iii-(Average Disk Bytes / Read & Average Disk Bytes / Write) --> Block Size,
iv- (Avg./Current Disk Queue Length) --> Outstanding or waiting IOPS,
v- (Disk Read Bytes/sec & Disk Write Bytes/sec) --> Throughput or Aggregate Throughput,
3.What values for -i, -f, and -t should be used to test the disk to extremes?