1 / 9

TCP on High-Speed Networks

TCP on High-Speed Networks. Sangtae Ha and Injong Rhee North Carolina State University. TCP is bad for large BDP path. TCP has been known for under-utilization for large BDP path because of its slow window increase (1/CWND for each ACK)

lumina
Download Presentation

TCP on High-Speed Networks

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. TCP on High-Speed Networks Sangtae Ha and Injong Rhee North Carolina State University

  2. TCP is bad for large BDP path • TCP has been known for under-utilization for large BDP path because of its slow window increase (1/CWND for each ACK) • Two TCP-SACK flows with background traffic in the testbed (400Mbps, 160ms RTT). Utilization(%) RTT

  3. 46 minutes 37 minutes 37 minutes 22,000 10Gbps 8000 Internet2 testing over 1Gbps • Internet2 path between NICT in Japan and UIC in Chicago • 1Gbps and 200ms RTT • One ideal TCP flow testing, followed by 1 TCP-SACK flow testing slow increase TCP Packet loss Packet loss Packet loss Packet loss big decrease cwnd Slow start Congestion avoidance Time (RTT)

  4. Results IDEAL Throughput TCP-SACK CWD RTT

  5. LAB test-bed

  6. Slow Start is bad for large BDP path • Slow Start probes an available bandwidth very fast (exponentially) • BUT, # of packet drops can be well beyond BDP, so it is more problematic for a large BDP path

  7. LAB Testbed testing • Linux 2.6.23.9 • Bandwidth: 400Mbps • Two TCP-SACK flows • 40ms RTT vs 280ms RTT

  8. Results • 40ms vs 280ms RTT

  9. File completion time demo • Compare the file completion time between TCP-SACK flow and I-Protocol flow

More Related