The QoS volume name (Workload)
The QoS workload ID (ID)
Input/output operations performed per second (IOPS)
Throughput in kilobytes per second (KB/s) or megabytes per second (MB/s) as appropriate (Throughput)
Latency observed per request in microseconds (us) or milliseconds (ms) as appropriate (Latency)

The results displayed per iteration are sorted by IOPS. Each iteration starts with a row that displays the total IOPS used across all volumes. Other columns in this row are either totals or averages.

Parameters

[-node {<nodename>|local}] - Node: Selects the volumes that match this parameter value. If you do not specify this parameter, the command displays data for the entire cluster.
{ [-rows <integer>] - Number of Rows in the Output: Specifies the number of busiest QoS policy groups to display. The default setting is 10. The allowed range of values is 1 to 20.
| -vserver <vserver name> - Vserver Name: Specifies the Vserver to which the volume belongs.
-volume <volume name> - Volume Name }: Selects the performance data that match this parameter value. Enter a complete volume name or press the <Tab> key to complete the name. Wildcard query characters are not supported.
[-iterations <integer>] - Number of Iterations: Specifies the number of times the display is refreshed before terminating. If you do not specify this parameter, the command iterates until interrupted by Ctrl-C.
[-refresh-display {true|false}] - Toggle Screen Refresh Between Each Iteration: Specifies the display style. If true, the command clears the display after each data iteration. If false, the command displays each data iteration below the previous one. The default is false.
[-show-flexgroup-as-constituents {true|false}] - Display Flexgroups as Constituents: If the parameter is specified and if the value is true, it will display data for FlexVols and Flexgroup Constituents. Otherwise it will display data for FlexVols and Flexgroups.

Examples

cluster1::> qos statistics volume performance show -iterations 100 -rows 3
Workload            ID     IOPS       Throughput    Latency
--------------- ------ -------- ---------------- ----------
-total-              -       97         1.90MB/s   216.87ms
vol_2-wid104       104       28         1.75MB/s   412.78ms
vol_1-wid103       103       25       100.00KB/s   169.16ms
vs1vol0-wid102     102       13        52.00KB/s   403.78ms
-total-              -       98      1276.00KB/s    89.98ms
vs1vol0-wid102     102       28       112.00KB/s    80.70ms
vol_1-wid103       103       19        76.00KB/s   114.72ms
vol_2-wid104       104       17      1088.00KB/s   257.60ms
-total-              -       78      1152.00KB/s   225.22ms
vol_1-wid103       103       17        68.00KB/s   452.27ms
vol_2-wid104       104       16      1024.00KB/s   419.93ms
vs1vol0-wid102     102       15        60.00KB/s   210.63ms

The example above displays the system performance for the 3 volumes with the highest IOPS and it refreshes the display 100 times before terminating.

cluster1::> qos statistics volume performance show -vserver vs0 -volume vs0_vol0 -iterations 100
Workload            ID     IOPS       Throughput    Latency
--------------- ------ -------- ---------------- ----------
-total-              -     1278       639.17KB/s   404.00us
vs0_vol0-wid1..  15658      526       263.17KB/s   436.00us
-total-              -     1315       657.33KB/s    86.00us
vs0_vol0-wid1..  15658      528       264.17KB/s    88.00us
-total-              -     1220       609.83KB/s   418.00us
vs0_vol0-wid1..  15658      515       257.33KB/s   531.00us
-total-              -     1202       600.83KB/s   815.00us
vs0_vol0-wid1..  15658      519       259.67KB/s   924.00us
-total-              -     1240       620.17KB/s   311.00us
vs0_vol0-wid1..  15658      525       262.50KB/s   297.00us

The example above displays the system performance for volume vs0_vol0 in Vserver vs0 and it refreshes the display 100 times before terminating.