TCP global synchronization

From Wikipedia, the free encyclopedia

You have new messages (last change).

TCP global synchronization in computer networks can happen to TCP/IP flows during periods of congestion because each sender will reduce their transmission rate at the same time when packet loss occurs.

Routers on the Internet normally have packet queues, to allow them to hold packets when the network is busy, rather than discarding them.

Because routers have limited resources, the size of these queues is also limited. The simplest technique and most efficient to limit queue size is known as tail drop. The queue is allowed to fill to its maximum size, and then any new packets are simply discarded, until there is space in the queue again.

This causes problems when used on TCP/IP routers handling multiple TCP streams, especially when bursty traffic is present. While the network is stable, the queue is constantly full, and there are no problems except that the full queue results in high latency. However, the introduction of a sudden burst of traffic may cause large numbers of established, steady streams to lose packets simultaneously.

TCP has automatic recovery from dropped packets, which it correctly interprets as congestion on the network. The sender reduces its sending rate for a certain amount of time, and then tries to find out if the network is no longer congested by increasing the rate again. This is known as the slow-start algorithm.

Almost all the senders will use the same time delay before increasing their rates. When these delays expire, at the same time, all the senders will send additional packets, the router queue will again overflow, more packets will be dropped, the senders will all back off for a fixed delay... ad infinitum.

This pattern of each sender decreasing and increasing transmission rates at the same time as other senders is referred to as global synchronization and leads to inefficient use of bandwidth, due to the large numbers of dropped packets, which must be retransmitted.

This problem has been the subject of much research. The consensus appears to be that the tail drops algorithm is the leading cause of the problem, and other queue size management algorithms such as Random Early Detection (RED) will reduce the likelihood of global synchronisation, as well as keeping queue sizes down in the face of heavy load and bursty traffic.

Connectionless protocols such as UDP do not experience global synchronization because they ignore (or are not aware of) packet loss.

[edit] See also

[edit] References

  • Vegesna, Srinivas (2001). IP Quality of Service, chap. 6. Cisco press. ISBN 1-57870-116-3.

[edit] External links

This article is uncategorized.

Please help improve this article by adding it to one or more categories, so it may be associated with related articles (how?). Please remove this tag after categorizing.
This page has been tagged since December 2006.
Retrieved from "http://en.wikipedia.org../../../t/c/p/TCP_global_synchronization_70ef.html"