PCP: Efficient Endpoint Congestion Control To appear in NSDI, 2006 Thomas Anderson, Andrew Collins,...
-
date post
22-Dec-2015 -
Category
Documents
-
view
214 -
download
0
Transcript of PCP: Efficient Endpoint Congestion Control To appear in NSDI, 2006 Thomas Anderson, Andrew Collins,...
PCP: Efficient Endpoint Congestion Control
To appear in NSDI, 2006
Thomas Anderson, Andrew Collins, Arvind Krishnamurthy and John ZahorjanUniversity of Washington
Presented by Karl DengApril 11, 2006
PCP -- Probe Control Protocol
Probe Detect whether the network can currently support a test rate
End-to-end approach
Emulates network-based control “Request and Set”
Overview
1. Minimize transfer time
2. Negligible packet loss & low queue variability
3. Resources are fully allocated if there is sufficient demand
4. Fairness
5. Stable system even under high loads
Design Goals
1. Minimize transfer time
Design Goals
Common Case -- Most network paths are idle most of the time.
Most transfers are relatively short Startup efficiency is particularly important.
TCP congestion control was designed at a time when links were thin and usually fully utilized Efficiency loss of slow start is minimal
2. Negligible packet loss & low queue variability
Design Goals
Packet loss: Queue overflow Can we prevent queues from overflow ?
Large queuing delays unnecessarily delay interactive response time and disrupt real-time traffic. Can we eliminate queues that might build up at routers?
1. Minimize transfer time2. Negligible packet loss & low queue variability3. Resources are fully allocated if there is sufficient demand4. Fairness5. Stable system even under high loads
Design Goals
Goals of PCP:Achieves rapid startup, small queues, and low loss rates, and that the it does not compromise eventual efficiency, fairness and stability.
Moderate sized flows on idle links
Interactive applications
Applications demanding minimally variable response times
TCP managed networks perform poorly for these applications!
Application Examples
Test a target rate by sending a short probe.
Given a successful test, senders immediately increase their base rate by the target rate of the probe.
Two important techniques:
Probe control: how to vary the test rates?
Using history: achieves constant startup time
Goal 1. Minimize transfer time Direct Jump
Exponential increase and decrease
Start with a baseline rate: One maximum sized packet per round-trip. Double the attempted rate increase after each successful probe. Halve the attempted rate increase after each unsuccessful probe.
Probe Control
Time
Rate
Probe
Probe
ChannelCapacityProbe
Direct Jump
Using History
Keep history information about the base rates previously used to each Internet address
Set the initial probe rate based on previous base rate.
Allows the end host to usually identify the optimal rate within two round trip times.
Direct Jump
Goal 2. Negligible packet loss & low queuevariability Rate compensation
Eliminate queues at routers:
Notice queue-buildups: Reduce the sending rate by a factor of (Δout – Δin ) /Δout
Detect persistent queueing: Reduce the sending rate by a factor of (max-delay – min-delay) / max-delay
Transmit the baseline packets in a paced manner (equally spaced) at the base rate.
Monitor the gap between baseline PCP packetsΔin -- gap used by the senderΔout -- gap observed at the receiver
Monitor the one-way delays of baseline PCP packetsmax-delay -- maximum one-way delay (maxdelay) observed in the previous round trip timemin-delay -- minimum observed one-way delay (will time out)
Baseline Packets
Send packet train spaced at an interval to achieve desired rate
-- Currently, five packets whose size could be varied
Check for queuing delays based on reception times
Probes
Both are paced packets.
Probes: short, high-rate bursts (sent at a test rate)Baseline packets: regular data traffic (sent at the base rate)
Impact of a Probe is independent of its test rate.Easy to test aggressively without fear of disrupting existing connections.
Comparison of Baseline Packets & Probes
Time
Rate
Probe
Probe
ChannelCapacityProbe
Conclusion
1. Minimize transfer time Direct Jump
- Probe: detect whether the network can currently support a test rate- Probe control: how to vary the test rates?- Using history: achieves constant startup time
2. Negligible packet loss & low queue variability Rate compensation
- Monitor the gap and one-way delays of baseline packets- Infer the queuing status and reduce base rate.