Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: dpreed@reed.com
To: "Mikael Abrahamsson" <swmike@swm.pp.se>
Cc: "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] BBR congestion control algorithm for TCP innet-next
Date: Wed, 21 Sep 2016 12:57:23 -0400 (EDT)	[thread overview]
Message-ID: <1474477043.80738799@apps.rackspace.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1609210818150.1477@uplift.swm.pp.se>

bittorrent is a kind of "FTP" rather than semi-isochornous (i.e. rate-bounded) "TV" in my personal classification.  As I'm sure you know, the two are quite different in their effects on congestion and their handling of congestion.

The idea that bittorrent dominated the Internet traffic volume at any point in time in the past is just plain not credible.  And an observation of one's own personal household by a high-end network user is not extrapolatable at scale.

(for example, it would require that all enterprise traffic through the Internet be dominated by bittorrent, unless enterprise traffic on the Internet is insignificant. There were never significant bittorrent users in enterprises, either connecting out from the companies' networks, or connecting "in" to the companies' externally facing sites).

In any case, there is no scienfic validity to "I seem to remember" claims.





On Wednesday, September 21, 2016 2:24am, "Mikael Abrahamsson" <swmike@swm.pp.se> said:

> On Tue, 20 Sep 2016, dpreed@reed.com wrote:
> 
>> I constantly see the claim that >50% of transmitted data on the Internet
>> are streaming TV. However, the source seems to be as hard to nail down
>> as the original claim that >50% of Internet traffic was pirated music
>> being sent over bittorrent.
> 
> It's my firm opinion that in the past 5-15 years (depending on market),
> more than 50% of Internet traffic is video, in some form or another.
> 
> This is from working at ISPs and seeing where traffic went. First it was
> bitorrent (pirated video), now it's Youtube, Netflix and other kind of
> streaming video. I wouldn't call this "TV" though.
> 
> In my household (2 adults, 1 6 year old), 75% of the average weekly
> traffic by volume, is over IPv6. I haven't checked in detail, but my guess
> is that Youtube+Netflix is the majority of this traffic. I come to this
> conclusion by looking at when the traffic occurs and what the traffic
> levels are, and from remembering what was done at the time.
> 
> --
> Mikael Abrahamsson    email: swmike@swm.pp.se
> 



  reply	other threads:[~2016-09-21 16:57 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-17 21:11 dpreed
2016-09-17 21:33 ` Dave Taht
2016-09-19 20:26   ` Dave Taht
2016-09-20 20:27     ` dpreed
2016-09-21  6:24       ` Mikael Abrahamsson
2016-09-21 16:57         ` dpreed [this message]
2016-09-21  7:32       ` Alan Jenkins
2016-09-21 17:04         ` dpreed
2016-09-21 18:00           ` Mikael Abrahamsson
2016-09-21 21:13             ` dpreed
2016-09-21 18:42       ` Alan Jenkins
2016-09-21 21:10         ` dpreed

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/cerowrt-devel.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1474477043.80738799@apps.rackspace.com \
    --to=dpreed@reed.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=swmike@swm.pp.se \
    /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