Congestion Control and Streaming Flashcards
How does problem of lack of knowledge of shared downstream bottleneck manifest itself?
- lost packets
- long delays
- congestion collapse
Congestion Collapse (short definition)
throughput less than bottleneck link
packets consume network resources only to get dropped later at a downstream link
Congestion Collapse causes
- spurious retransmission
2. undelivered packets
Solution to spurious retransmission
- better timers
2. TCP congestion control
How does TCP interpret packet loss? What does it do as a result?
Congestion. It will slow down as a consequence
What do senders do if no packets are dropped?
Increase sending rate
TCP increase algorithm behavior
Sender tests network to determine if network can sustain higher sending rate
TCP decrease algorithm behavior
Senders react to to congestion to achieve optimal loss rates, delays, and sending rates
RTT = 100 milliseconds
packet size = 1 kb (kilobyte)
window size = 10 packets
What is transmission rate in kbps?
800 kbps
Rate Based Approach to Rate Adjustment
- Sender monitors loss rate
- sender uses timer to modulate
(less common method)
Fairness vs Efficiency
Fairness is everyone getting ‘fair share’ and efficiency is when network resources are used well.
Where does high ‘fan in’ occur
between leaves and root of data center
data center attributes
- high ‘ fan in’
- high bandwidth, low latency workloads
- many parallel requests
TCP incast problem
throughput collapse resultant from many parallel requests in data center. Switches overflow buffers, causing underutilization of network.
This is a many to one issue
Causes bursty retransmission due to TCP timeouts
bursty retransmission cause
caused by TCP timeouts in TCP incast problem scenario
incast
drastic reduction in application throughput caused when servers all simultaneously request data
barrier synchronization
client/app may have many parallel threads and no forward progress can be made until all the responses for those threads are satisfied.