1. Sechang Son Computer Sciences Department University of Wisconsin-Madison sschang@cs.wisc.edu http://www.cs.wisc.edu/condor Network Bandwidth Regulation

2. www.cs.wisc.edu/condor Outline › Bandwidth Regulation Model › Goals and Approaches › Overall Scheme › Cedar’s Local Regulation › NetMnger’s Global Regulation › Future Work

3. www.cs.wisc.edu/condor Bandwidth Regulation Model

4. www.cs.wisc.edu/condor Goals › Controlled use of bandwidth › Not monopolizing network › Why not TCP?  TCP congestion control does not distinguish between user process and Condor process  We want to give more bandwidth to user process

5. www.cs.wisc.edu/condor Approaches › Focus on mechanism › No change to existing Cedar interface  Cedar = network layer of condor  Compatibility issue › Simple manager implementation

6. www.cs.wisc.edu/condor Overall Scheme

7. www.cs.wisc.edu/condor Overall Scheme  

8. www.cs.wisc.edu/condor Overall Scheme  

9. www.cs.wisc.edu/condor Overall Scheme   

10. www.cs.wisc.edu/condor Overall Scheme   

11. www.cs.wisc.edu/condor Overall Scheme X  

12. www.cs.wisc.edu/condor Cedar’s Local Regulation › Bandwidth Allocation › Bandwidth Regulation › Congestion Detection & Control

13. www.cs.wisc.edu/condor Bandwidth Allocation › (window, maxBytes, maxPercent)  Do not send, in any case, more than maxBytes bytes during window sec  If congestion occurs, back off to maxPercent % of what you could send at the time of congestion

14. www.cs.wisc.edu/condor Bandwidth Regulation › Moderate level of short burst is allowed › Can’t saved too much bandwidth for later use › When (100M, 100sec, 80%) is given  Can send up to 10M(> 6M) during 6sec  Can’t send 90M during 25sec, even if only 10M has been sent during 75sec

15. www.cs.wisc.edu/condor Congestion Detection & Control › Detection  Measure time taken to send a packet  Check the number of bytes sent by TCP › Control  Back off to the given percent in allocation  Remain backed off for a while  Gradually try more bandwidth

16. www.cs.wisc.edu/condor

18. NetMnger’s Global Regulation › Bandwidth (Re)Allocation › Congestion Control

19. www.cs.wisc.edu/condor Bandwidth (Re)Allocation › Even distribution of bandwidth among Condor connections › Periodic polling of network usage and condition › Reallocation occurs when  Extra bandwidth needed: new connection  Free bandwidth found: close report, less usage  Congestion reported

20. www.cs.wisc.edu/condor Congestion Control › If any of Cedar reports congestion, NetMnger backs off every Cedar sharing the network › If every Cedar reports No congestion, NetMnger gives the original bandwidth to each Cedar

21. www.cs.wisc.edu/condor

22. Further Work › The study of relationship to TCP’s congestion control › Congestion Avoidance  E.g TCP Vegas mechanism

23. www.cs.wisc.edu/condor Thank You sschang@cs.wisc.edu