PFLDnet 2007

International workshop on protocolsfor fast long-distance networks

7-9 February, Los Angeles

TCP algorithms

Fairness

Hardware – a good interaction (rare!)

An experiment shows something odd...• Input rate | C flow 1 | C flow 2 A B | Av Max Min | Av Max Min1000 1000 | 800 988 666 | 188 323 0 800 800 | 197 197 197 | 792 791 0 500 500 | 494 494 494 | 494 494 494 800 600 | 569 574 566 | 419 423 414

• What was expected if switch queuing was fairInput rate | C flow 1 | C flow 2 A B | Av Max Min | Av Max Min1000 1000 | 500 500 500 | 500 500 500 800 800 | 500 500 500 | 500 500 500 500 500 | 500 500 500 | 500 500 500 800 600 | 600 600 600 | 400 400 400

... and we learn something newFrom: Val OlivaSent: Tuesday, February 13, 2007 10:46 AMTo: Gordon Vick; Bob Schiff; David WhiteSubject: Re: Performance of FESX424

I read the results and it is not clear to me were we failed. I mean, here’s what I saw:

1. The software used, 2.0.00, was very old.

2. We have features such as Dynamic Buffer Allocation that allows for oversubscription. Albeit available, the default DBA settings were meant for line rate performance and not oversubscribed conditions.

3. Non-blocking switches operate at a faster clock, and don’t work well when host are slow to send packets (or have increased IPG). Again, the FESX’s IPG can be tuned.

Foundry knows the requirements for Grid Computing and that is why we have those features. Foundry also knows the requirements for VoIP (a mass market) and our switches default setting are tuned for that market.

Testing

Web sites

5th wil.cs.caltech.edu/pfldnet20074th www.hpcc.jp/pfldnet20063rdwww.ens-lyon.fr/LIP/RESO/pfldnet20052nd www-didc.lbl.gov/PFLDnet20041st datatag.web.cern.ch/datatag/pfldnet2003

6th University of Manchester, UK, February 2008Announcement on end2end-interest at postel org