Skip to main content
NetApp Knowledge Base

Latency from CPU_protocol for extremely bursty SAN workloads

Views:
568
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
perf
Last Updated:

Applies to

ONTAP 9

Issue

  • High latency observed for extremely bursty SAN workloads. Breakdown of the latency shows high latency on Network & Protocol processing, this could be observed in various ways:
    • Perfstat: Delay from CPU_protocol
    • PerfArchive: Delay from Network
    • Other performance monitoring tools like NetApp Harvest/Grafana will have similar latency breakdowns. 
    • Command Line: qos statistics workload latency show or qos statistics volume latency show has the latency from Network

Example:

Latency from CPU_protocol for extremely bursty SAN workloads

  • The high latency from CPU_protocol/Network is observed when there is no CPU contention in SAN processing CPU Domains, such as SSAN_Ex

Example: sysstat -M 1(Diag Mode)

Latency from CPU_protocol for extremely bursty SAN workloads

Note: If there is an overall CPU contention, then the delay from CPU_protocol/Network is expected, the discussion here wouldn't apply. 

  • The following KB would help detect if there exists an extremely bursty workload

How to identify transient workload bursts using "sysstat" command

 

 

 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.