Help

● Press and hold Ctrl and click a column header to create a sort order. A number appears in the column header to indicate the
order of the sort.
● Click a sorted column header to remove the number and clear a sort order.
● Rearrange columns by clicking the column header, and dragging the column to the desired location.
Viewing the Rebuild Status dashboard
1. From the GUI main menu, click Performance.
2. Click + and select Add Rebuild Dashboard.
Virtual Volumes dashboard
The Virtual Volumes Performance dashboard
The Virtual Volumes Performance Dashboard shows performance metrics of the top 100 busiest volumes, ranked by total
IOPS. By default, these volumes are displayed from the busiest IOPS (throughput) volumes to the least busy. You can sort the
data in each column in ascending or descending order. Note that when you sort data in other columns, the data set is still the
top 100 volumes in the system based on IOPS.
The Virtual Volumes list automatically refreshes every 60 seconds, displaying data from the last 60 second period. Select a
volume in the list and then click VIEW CHARTS to display the Throughput, Bandwidth and Latency charts for the volume.
See the Virtual Volumes Throughput chart, Virtual Volumes Latency chart or Virtual Volumes Bandwidth chart for specific
information for each chart.
You can view metrics only for the virtual volumes in the cluster you are logged into. To view metrics for virtual volumes on a
second cluster, open another browser, connect to the second cluster, and then open the Virtual Volumes dashboard.
NOTE: You cannot add virtual volume charts to other dashboards or add other charts to the Virtual Volumes Dashboard.
The Virtual Volumes Performance Dashboard shows the following performance statistics for each virtual volume listed:
● IOPS — Total count of read and write operations.
● Reads (KB/s) — Bandwidth for read operations.
● Writes (KB/s) — Bandwidth for write operations.
● Read Avg Latency (usec) — Average latency or response time for read operations.
● Write Avg Latency (usec) — Average latency or response time for write operations.
General guidelines
● For Latency statistics:
○ Satisfactory latency or response time depends heavily on the application's requirements.
○ It is difficult to give recommended values for front-end latency since it depends heavily on back-end latency.
○ In general, read or write latency values under 10msec are good, and greater than 100msec is usually cause for concern.
○ Different volumes will likely have different thresholds for what is acceptable. 10msec might be acceptable to one
application but totally unacceptable to another.
● For Throughput and Bandwidth statistics:
○ There is recommendation for what is good or bad for IOPS and KB/s. It is typically what the application requests of the
volume.
○ If values for these metrics are unsatisfactory, be aware of resource bottlenecks such as over-saturated front-end ports,
or over-utilized metro node directors.
○ Identify performance-intensive applications such as nightly back-ups or data warehouse applications that might cause
other latency-sensitive applications to suffer. Identify these busy volumes and adjust accordingly so they do not conflict.
This includes actions such as moving them to their own front-end ports or directors (if possible), adjusting their
maximum outstanding operations counts (queue depths), or staggering their start times to avoid busy times.
Corrective actions
● Unsatisfactory virtual volume performance might be the symptom of poor storage volume performance.
Monitoring the system
49