3 ms·
You're totally correct that the performance is terrible when the actual network characteristics are something that the algorithm's "prior assumptions" thought w
by keithwinstein 12y ago
You're totally correct that the performance is terrible when the actual network characteristics are something that the algorithm's "prior assumptions" thought was impossible.
We think the same is true of traditional TCP. (For example, traditional TCP assumes that in-network buffers will be small, and therefore that it's acceptable to keep filling them until they start dropping packets, without harming delay-sensitive cross traffic too much. Today's Internet no longer matches TCP's implicit model, and the consequences are that you can't upload to YouTube and use Skype at the same time on a consumer Internet connection. We think it's better to at least make the assumptions explicit!)
In the second paper (now posted), we have improved the initial results in that we can now train a RemyCC that outperforms TCP CUBIC-over-sfqCoDel over a 1000-fold range of link rates (instead of 10x in the first paper). But the same basic point still holds.
- dtaht 12y agoMy problem with the new paper is that it computes for a baseline rtt of 100 or 150ms. Real world average rtts are in the range of 4 ms for Google fiber 18 ms for fios and 38 ms for cable, with the ethernet rtt in a Datacenter far lower than that. I would be very happy to see Remy produce a CC for these rtts one day also.
- keithwinstein 12y agoStay tuned... or bug Anirudh for a sneak preview when you see him at SIGCOMM. (Hi Dave!)
- dtaht 12y agoI put up all I have to say on the subject at: https://lists.bufferbloat.net/pipermail/bloat/2014-August/002045.html https://lists.bufferbloat.net/pipermail/bloat/2014-August/00...
- yxhuvud 12y agoWould it be possible to have an external monitor that detects what assumptions is holding? (and either recomputate the algorithm or change to one that is working)?