<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Tcp on Mi&amp;Bee Blog</title><link>/en/categories/tcp/</link><description>Recent content in Tcp on Mi&amp;Bee Blog</description><generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>蓝宝石的傻话</managingEditor><lastBuildDate>Mon, 10 Apr 2017 00:00:00 +0000</lastBuildDate><atom:link href="/en/categories/tcp/rss.xml" rel="self" type="application/rss+xml"/><item><title>A Simple BBR Test on Linode</title><link>/en/archives/linode-bbr-test/</link><pubDate>Mon, 10 Apr 2017 00:00:00 +0000</pubDate><guid>/en/archives/linode-bbr-test/</guid><description>&lt;h2 id="overview"&gt;Overview:&lt;/h2&gt;
&lt;p&gt;TCP BBR solves two problems:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Fully utilizing bandwidth on network links with some packet loss. Suitable for high-latency, high-bandwidth network links.&lt;/li&gt;
&lt;li&gt;Reducing buffer occupancy on network links, thereby lowering latency. Suitable for users with slow access networks.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;I remember when BBR was first merged into the Linux 4.9 kernel in 2017, this congestion control algorithm proposed by Google was extremely popular in the tech community. At the time, I was doing cross-border file transfers on Linode, where packet loss was commonplace, so I wanted to test the results firsthand.&lt;/p&gt;</description></item></channel></rss>