FACTOID # 163: Only 4% of married women in Chad are using contraceptives.
 
 Home   Encyclopedia   Statistics   Countries A-Z   Flags   Maps   Education   Forum   FAQ   About 
 
 
 
WHAT'S NEW
RECENT ARTICLES
More Recent Articles »
 

SEARCH ALL

FACTS & STATISTICS    Advanced view

Search encyclopedia, statistics and forums:

 

 

(* = Graphable)

 

 


Encyclopedia > Congestion collapse

In data networking and queueing theory, network congestion occurs when incremental increases in offered load lead either only to small increases in network throughput, or to an actual reduction in network throughput.


Network protocols which use aggressive retries to compensate for packet loss tend to keep systems in a state of network congestion even after the initial load has been reduced to a level which would not normally have induced network congestion. Thus, networks using these protocols can exhibit two stable states under the same level of load. The stable state with low throughput is known as congestion collapse, a term which was first defined by John Nagle in RFC 896, written in 1984, when he identified problems with early implementations of the TCP network protocol over parts of the very early Internet. Congestion collapse is a condition where a system such as a data network has settled under load into a state where traffic demand is high but little useful throughput is available, with high levels of packet loss, delay, and delay variation.


Experience of widespread congestion collapse in the Internet in 1987 led to further improvements of the TCP congestion control mechanisms.


Modern networks use congestion control and network congestion avoidance techniques to try to avoid congestion collapse. These include exponential backoff in protocols such as TCP and Ethernet, and fair queueing in devices such as routers.


RFC 2914 addresses the subject of congestion control in detail.


See also:

External links


  Results from FactBites:
 
RFC 2914 (rfc2914) - Congestion Control Principles (4803 words)
As discussed in Section 3, congestion collapse was first reported in the mid 1980s [RFC896], and was largely due to TCP connections unnecessarily retransmitting packets that were either in transit or had already been received at the receiver.
Congestion collapse from undelivered packets arises when bandwidth is wasted by delivering packets through the network that are dropped before reaching their ultimate destination.
Because congestion collapse from undelivered packets consists of packets that waste valuable bandwidth only to be dropped downstream, this form of congestion collapse is not possible in an environment where each flow traverses only one congested link, or where only a small number of packets are dropped at links downstream of the first congested link.
Federal Highway Administration Home Page (736 words)
Congestion is increasingly being recognized as a problem of national importance that adversely affects both the economy and quality of life.
In 2003, congestion cost an estimated $63 billion in wasted fuel and time alone.
The final rule on Work Zone Safety and Mobility was published in the Federal Register (69 FR 54562) on September 9, 2004 with an effective date of October 12, 2007.
  More results at FactBites »


 
 

COMMENTARY     


Share your thoughts, questions and commentary here
Your name
Your comments

Want to know more?
Search encyclopedia, statistics and forums:

 


Lesson Plans | Student Area | Student FAQ | Reviews | Press Releases |  Feeds | Contact
The Wikipedia article included on this page is licensed under the GFDL.
Images may be subject to relevant owners' copyright.
All other elements are (c) copyright NationMaster.com 2003-5. All Rights Reserved.
Usage implies agreement with terms, 1022, m