3 ms·
This has nothing to do with Google's politics. TCP is broken for modern networks, and the faster we ditch it for a protocol capable of reliable pipes with low l
by trevyn 9y ago
This has nothing to do with Google's politics. TCP is broken for modern networks, and the faster we ditch it for a protocol capable of reliable pipes with low latency and high throughput, the better off we'll all be.
- minikites 9y agoNot all networks are modern, what about the unreliable networks in most of the developing world?
- trevyn 9y agoQUIC still works better than TCP on these networks, but the benefits are not as dramatic.
- tybit 9y agoThat doesn't seem to be supported by the article? "While it outperforms TCP in a wide range of scenarios, we found that it underperforms in the presence of packet reordering and on resource-constrained mobile devices."
- trevyn 9y ago1) "We shared this result with a QUIC engineer, who subsequently informed us that the QUIC team is experimenting with dynamic threshold and time-based solutions to avoid falsely inferring loss in the presence of reordering." 2) "We find that, similar to the desktop environment, in mobile QUIC outperforms TCP in most cases; however, its advantages diminish across the board... The reason for this behavior is that QUIC runs in a userspace process, whereas TCP runs in the kernel." (i.e. putting it in the kernel should help.) https://conferences.sigcomm.org/imc/2017/papers/imc17-final39.pdf https://conferences.sigcomm.org/imc/2017/papers/imc17-final3...