Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Is Google Drive using QUIC? If so, then its using the same BBR congestion algorithm as the bbr tcp stack, and BBR's algorithm which does not view loss as congestion will help a lot.

It would be interesting to re-try the experiment on Linux or FreeBSD using BBR as the TCP stack and see if the results are any better for dropbox.

FWIW, my corp openvpn is kinda terrible. My upload speeds via the vpn did not improve at all when I moved and upgraded from 10Mb/s to 1Gb/s upstream speeds. When I switched to BBR, my bandwidth went from ~8Mb/s -> 60Mbs, which I think is the limit of the corp vpn endpoint.



Looking at the flows on my network while uploading a file, it seems Google Drive's mac client just uses regular old TCP, same for the website.


QUIC is UDP, and TCP does not use CCA in userspace.


QUIC absolutely uses congestion control. See section 6 here https://tools.ietf.org/id/draft-ietf-quic-recovery-26.html


No denying in that.


QUIC does run in user space, and also uses congestion controllers running inside the QUIC stack, in user space.

(I work on a QUIC implementation in Rust.)


QUIC is a protocol... "...CCA in userspace" CCA stands for congestion control algorithm.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: