Network Performance and Quality of Service 8. Congestion Control in Data Networks Introduction Congestion occurs when number of packets transmitted approaches network capacity Objective of congestion control: RQ12 keep the number of packets that are entering/within the network below the level at which performance drops off dramatically 2 Queuing Theory Data network is a network of queues If at any queue … arrival rate > transmission rate then, queue size grows without bound and packet delay goes to infinity General rule of thumb … Design point: ρ = Lλ/R < .8 RQ12 3 At Saturation Point … Two Possible Strategies at Node … Discard any incoming packet if no buffer available Exercise flow control over neighbors over neighbors RQ12 May cause congestion to propagate throughout network 4 Queues in Nodes and Networks (delay propagation) RQ12 5 Ideal Performance Infinite Buffers, No Congestion Control Overheads No variable overhead for packet transmission or congestion control Throughput increases with offered load up to full capacity Packet delay increases with offered load approaching infinity at full capacity Power = throughput / delay, or a measure of the balance between throughput and delay RQ12 Higher throughput results in higher delay 6 Ideal Network Utilization Load: Ts = L/R Power: RQ12 Ratio of Normalized Throughput to Delay 7 Practical Performance Finite Buffers, Congestion Control Overheads RQ12 Non-zero packet processing overhead With no congestion control, increased load eventually causes moderate congestion: throughput increases at slower rate than load Further increased load causes packet delays to increase and eventually throughput to drop to zero 8 Effects of Congestion (if not controlled) What’s happening here? • buffers fill • packets discarded • sources re-transmit • routers generate more traffic to update paths • good packets resent • delays propagate RQ12 9 Common Congestion Control Mechanisms Backpressure Choke packet RQ12 Implicit congestion signaling Explicit congestion signaling 10 Congestion Control Backpressure Choke packet Specific message back to source e.g., ICMP Source Quench Implicit congestion signaling Congested node requests sender to reduce rate Useful only on a logical connection basis Requires hop-by-hop flow control mechanism Source detects congestion from transmission delays and lost packets and reduces flow Explicit congestion signaling RQ12 Network alerts the end systems to growing congestion End systems take steps to reduce offered load. 11 Explicit congestion signaling Direction Categories RQ12 Backward Forward Binary Credit-based rate-based 12 Traffic Management in Congested Network – Some Considerations Fairness Quality of Service (QoS) Various flows should “suffer” equally Last-in-first-discarded may not be fair Flows treated differently, based on need Voice, video: delay sensitive, loss insensitive File transfer, mail: delay insensitive, loss sensitive Interactive computing: delay and loss sensitive Reservations RQ12 Policing: excess traffic discarded or handled on best-effort basis 13
© Copyright 2025 Paperzz