Network Management
ASYNC_NETWORK_IO SQL WAIT Stats
This content will describe SQL Server wait type that can be encountered more or less commonly, which includes the description, steps that should be taken, and additional resources that could be used for troubleshooting.
First published date
10/8/2021 12:45 PM
Last published date
7/26/2022 4:11 AM
Overview
This is usually a sign of network latency between the client and the server.
Product section
Network Performance Monitor
Cause
Description
Accumulates while requests are waiting on network I/O to complete. A common cause of this wait type is when client applications cannot process data as fast as SQL Server can provide it. When this occurs SQL Server must wait until the client is ready. Other causes include network bottlenecks and sending large volumes of data across the network
Calling Application is not Processing Results Fast Enough - the most common cause of this wait is an application server that is low on resources, e.g. CPU is spiked at 100%. Other causes could be an application that reads data and then does other processing, e.g. read a row, run another process that takes several seconds or minutes.
Network Hardware Problems - this is rarely the cause, but review counters such as Batch Requests per second (values over 3000 for a 100MB network card are getting excessive) and Network Interface: Current Bandwidth (values over 0.6 are getting excessive).
Accumulates while requests are waiting on network I/O to complete. A common cause of this wait type is when client applications cannot process data as fast as SQL Server can provide it. When this occurs SQL Server must wait until the client is ready. Other causes include network bottlenecks and sending large volumes of data across the network
Calling Application is not Processing Results Fast Enough - the most common cause of this wait is an application server that is low on resources, e.g. CPU is spiked at 100%. Other causes could be an application that reads data and then does other processing, e.g. read a row, run another process that takes several seconds or minutes.
Network Hardware Problems - this is rarely the cause, but review counters such as Batch Requests per second (values over 3000 for a 100MB network card are getting excessive) and Network Interface: Current Bandwidth (values over 0.6 are getting excessive).
Resolution
Suggested solutions
The content posted herein is provided as a suggestion or recommendation to you for your internal use. The information set forth herein may come from third party website or customers. SolarWinds is not liable for any downtime or any issue that may occur if you perform the following suggestions on the link provided. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment.
- Reduce the amount of data sent over the network by selecting only the required rows and columns
- Ensure that Network Packet Size in connection strings is of an appropriate size. If the instance is doing bulk loads try increasing packet size to see whether this improves throughput.
- Add additional or upgrade network interface
- Remove any additional applications that are using network interfaces
The content posted herein is provided as a suggestion or recommendation to you for your internal use. The information set forth herein may come from third party website or customers. SolarWinds is not liable for any downtime or any issue that may occur if you perform the following suggestions on the link provided. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment.