Transmission Control Protocol (TCP) Loopback Optimization

08/31/2016

2 minutes to read

In this article

Updated: May 9, 2012

Applies To: Windows Server 2012

Transmission Control Protocol (TCP) loopback optimization

Many applications use the TCP/IP loopback path to provide interprocess communications. While convenient from a development and deployment perspective, the TCP/IP loopback path can become a bottleneck for applications that require very high performance or very low latency.

To address the needs of these kinds of applications, Windows Server 2012 introduces a TCP Loopback performance enhancement that provides an optimized fast path. The optimized fast path increases the achievable TCP send and receive rates, and reduces latency and jitter for low latency scenarios.

TCP loopback optimization does not cause any disparity in performance between IPv4 and IPv6 networks.

The optimized loopback path works in virtualized environments. Loopback is defined as an inter-process communication mechanism for both processes on the same computer. Because of this, VM-to-VM optimization — when both VMs are installed in the same physical host — is not provided. The boundary for optimization between VMs in this case is the individual VM boundary.

With TCP loopback optimization, you are provided the choice to use either registered (Winsock RIO) sockets or Winsock to make use of the optimized fast path. You can observe when the connections take the slow path rather than the optimized fast path.

The optimized loopback path is available for developers to programmatically control on a per-connection basis.

In addition, TCP loopback fast path is an optimization for newly written applications, and does not provide performance improvements for existing applications.

TCP loopback optimization is available on all versions of Windows Server 2012 and Windows 8. This feature is turned on whenever the Socket option for fast path is set for a connection, and utilizes the optimized fast path whenever the application has opted-in and the Windows Filtering Platform (WFP) filter driver is not present for that connection.

The TCP loopback fast path is enabled by the socket IOCTL SIO_LOOPBACK_FASTPATH applied to the sending and receiving sockets.