Skip to main content
NetApp Knowledge Base

Latency seen on Windows client on SQL Index Rebuild for a DB on 16 LUNs from CVO-HA

  1. Last updated
  2. Save as PDF
Views:
223
Visibility:
Public
Votes:
0
Category:
cloud-volumes-ontap-cvo
Specialty:
san
Last Updated:

Applies to

  • Microsoft  Structured Query Language (MS SQL) Index Rebuild
  • SQL Database (DB) ISCSI LUNs on CVO
  • read latency on Client side
  • Microsoft Azure
  • Cloud Volumes ONTAP High Availability (CVO HA)
  • Active-Passive LUN distribution on CVO
  • Windows client and Azure CVO in same vNET and no firewall
  • CVO HA NICs for ISCSI fine

Issue

  • ISCSI read latency upto 15 to 20ms seen on Windows client on SQL Index Rebuild for a DB spread on 16 LUNs from CVO-HA.
  • LUNs are configured one each per volume and all volumes located on one node on CVO-HA in active passive configuration.
  • CVO side latency measured from disks to network layers shows average of 5ms.
  • Packet traces between windows client and Azure CVO HA showed packet drops and old congestion control in play.

 

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.