From: Otto Solares <solca@guug.org>
To: Stephen Hemminger <shemminger@vyatta.com>
Cc: Bloat@lists.bufferbloat.net
Subject: Re: [Bloat] Fwd: Identifying TCP congestion control algorithms, and measurement results
Date: Wed, 23 Mar 2011 13:14:15 -0600 [thread overview]
Message-ID: <20110323191415.GH30600@guug.org> (raw)
In-Reply-To: <20110323081308.10198612@nehalam>
On Wed, Mar 23, 2011 at 08:13:08AM -0700, Stephen Hemminger wrote:
> This showed up on the end-to-end mailing list and might be of interest
> to this group. It is interesting how many hosts are still using BIC
> (probably RHEL/Centos 5). BIC is known to be broken and unfair.
Too those "web servers use abnormal slow start algorithms" could be
related to sites using IW10 or more for the initial cwnd:
http://blog.benstrong.com/2010/11/google-and-microsoft-cheat-on-slow.html
IW10 seems to be part now of mainline Linux since 2.6.37:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=356f039822b8d802138f7121c80d2a9286976dbd
-
Otto
> From: Lisong Xu <lisongxu2@gmail.com>
> Date: Tue, Mar 15, 2011 at 3:36 PM
> Subject: [e2e] Identifying TCP congestion control algorithms, and
> measurement results
>
>
> Greetings,
>
> We have recently developed a tool, called TCP Congestion Control
> Avoidance Identification (CAAI), for actively identifying the TCP
> congestion avoidance algorithm of a remote web server. We used CAAI to
> measure the TCP algorithms of the top 5000 web sites in February 2011,
> and got some preliminary results in which you might be interested.
>
> # Only 16.85~25.58% of web servers still use the traditional AIMD.
> # 14.36%, 15.82%, and 14.33% of web servers use BIC, CUBIC' (kernel
> 2.6.25 and before), and CUBIC (kernel 2.6.26 and after), respectively.
> Total = 44.51%.
> # 9.97% and 0.30~9.03% of web servers use CTCP' (Windows Server 2003
> and XP Pro x64) and CTCP (Windows Server 2008, Vista, and 7),
> respectively. Interestingly, CTCP' behaves very similar to HSTCP.
> Total = 10.27~19%.
> # Some web servers use non-default TCP algorithms (such as YEAH), some
> web servers use some unknown TCP algorithms which are not available in
> any major operating system family, and some web servers use abnormal
> slow start algorithms.
>
> More information is available at our project webpage
> http://cse.unl.edu/~xu/research/TCPcensus.html.
>
> Thanks
> Lisong
>
> --
> Lisong Xu, Associate Professor
> Computer Science & Engineering
> University of Nebraska-Lincoln
> http://cse.unl.edu/~xu
next prev parent reply other threads:[~2011-03-23 19:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-23 15:13 Stephen Hemminger
2011-03-23 18:06 ` Jonathan Morton
2011-03-23 19:14 ` Otto Solares [this message]
2011-03-23 20:36 ` Steve Bauer
2011-03-24 0:45 ` Otto Solares
2011-03-23 21:17 ` Aki Nyrhinen
2011-03-24 0:49 ` Otto Solares
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110323191415.GH30600@guug.org \
--to=solca@guug.org \
--cc=Bloat@lists.bufferbloat.net \
--cc=shemminger@vyatta.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox