<story><title>Employing QUIC Protocol to Optimize Uber’s App Performance</title><url>https://eng.uber.com/employing-quic-protocol/</url></story><parent_chain></parent_chain><comment><author>ctime</author><text>This YouTube video does a great job illustrating how well HTTP&amp;#x2F;2 works in practice.&lt;p&gt;&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;www.youtube.com&amp;#x2F;watch?v=QCEid2WCszM&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;www.youtube.com&amp;#x2F;watch?v=QCEid2WCszM&lt;/a&gt;&lt;p&gt;A lesser known *ownside to HTTP&amp;#x2F;2 over TCP solution was actually caused by one of the improvements - a single reusable (multiplexed) connection - that could end up stalled or blocked due to network issues. This behavior could go unnoticed over the legacy HTTP&amp;#x2F;1.1 connections due to browsers opening a hugh number of connections (~20) to a host, so when one would fail it wouldn&amp;#x27;t block everything.</text></comment>
<story><title>Employing QUIC Protocol to Optimize Uber’s App Performance</title><url>https://eng.uber.com/employing-quic-protocol/</url></story><parent_chain></parent_chain><comment><author>internals</author><text>What a great case study. Successfully shifting 80% of mobile traffic to QUIC for a 50% reduction in latency is amazing. QUIC and the ongoing work with multipath TCP&amp;#x2F;QUIC will be huge QoL improvements for mobile networking.</text></comment>