Skip to main content
NetApp Console local deployment

Investigate high throughput on a volume in NetApp Console local deployment

Contributors netapp-tonias netapp-ml94669

Use Workload Analyzer in NetApp Console local deployment to examine a volume's IOPS and throughput demand over time.

When a volume's workload is consuming more IOPS or throughput than expected, identify what's driving the demand. The throughput analysis section shows IOPS and MB/s with an optional read, write, and other breakdown so you can identify which type of I/O is driving high demand and whether that demand is trending toward a QoS limit.

If you open the analyzer from an alert or from volume inventory, the volume is already selected and you can focus on the time range and throughput charts.

Steps
  1. Open Workload Analyzer using one of the following methods:

    • From the Health menu, select Workload Analyzer, then search for and select the volume you want to investigate in the Volume field.

    • From the Storage > Fleets > Inventory page, navigate to a volume you want to analyze and select Analyze from the action menu.

    • From the Alerts > Overview page, select an alert for the volume you want to investigate, then select Analyze from the alert details.

  2. Set the Time Range to cover the period of high demand, then select Analyze.

  3. Scroll to the Throughput Analysis section.

  4. Open the View dropdown and select Breakdown (RWO).

    The charts split into read, write, and other components for both IOPS and MB/s. This lets you determine whether read-heavy access patterns, write-heavy patterns, or a combination is driving the demand.

  5. Use the component picker to enable or disable the metrics you want to examine:

    • Read IOPS and Write IOPS — operations per second by I/O direction

    • Read MB/s and Write MB/s — throughput in megabytes per second by I/O direction

    • Other IOPS and Other MB/s — metadata and other non-data operations

    • QoS IOPS Limit and QoS MB/s Limit — policy ceilings that appear only when the volume uses a QoS policy

    • Cloud Throughput — MB/s written to and read from the cloud, shown only for workloads that tier capacity to the cloud through FabricPool

  6. Hover over a peak in the chart to see the exact value and percentage breakdown for each component at that point in time.

    The hover tooltip also shows the average I/O size (throughput divided by IOPS) for each category, which can indicate whether the workload is performing large sequential I/O or small random I/O.

  7. Enable Show Forecast to project whether current throughput trends will reach the QoS IOPS or MB/s limit.

    If the forecast line is approaching a QoS limit line, ONTAP might throttle the workload soon.

  8. If you want to see aggregate demand without the breakdown, open the View dropdown and select Totals.

    The totals view shows a single IOPS line and a single MB/s line, which is useful for a quick overall demand summary.

After you finish

Use the throughput patterns you observe to decide what to do next:

  • If read IOPS are very high relative to write IOPS, consider whether read-ahead settings or caching can reduce the load on the volume.

  • If the workload is approaching or has reached the QoS IOPS or MB/s limit, use the QoS limit lines and related metric definitions to confirm throttling and decide whether you need to adjust the limit.

  • If throughput is high and latency is also elevated, check the Resource Utilization section to determine whether the underlying node or aggregate is under contention. Compare throughput peaks, latency spikes, and resource utilization over the same period.

  • If the analyzer shows rapid capacity or snapshot growth while demand is increasing, review the capacity and snapshot metrics to understand how that growth might affect the volume.