Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: dpreed@reed.com
To: "Alan Jenkins" <alan.christopher.jenkins@gmail.com>
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 17:10:21 -0400 (EDT)	[thread overview]
Message-ID: <1474492221.058911695@apps.rackspace.com> (raw)
In-Reply-To: <CANmMgnFZQ2KusNEcx+Dv56xsw2ZP+w6BfsNq8VZiBxvyDi7MSw@mail.gmail.com>

Don't want to dwell on this, but Sandvine is not an unbiased source.  And it is apparently the *only* source - and 50% is a LOT.  Even Trump and Clinton don't have 50% of the electorate each. :-)

Does Sandvine have the resources to examine a true sample of all Internet traffic?

Maybe the NSA does.



On Wednesday, September 21, 2016 2:42pm, "Alan Jenkins" <alan.christopher.jenkins@gmail.com> said:

> On 20/09/2016, dpreed@reed.com <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.
> 
> uh, ibid.
> 
> 50-60% "upstream bandwidth", 2010 and 2008 respectively.
> 
> I'm quite happy to believe the trend, at least. Do you have a
> preferred assessment or even a rebuttal (back of the envelope,
> whatever) for around that time?
> 
> BT for media is a real sweet spot.  Music particularly because people
> _collect_, though I don't know what the timeline would look like for
> music v.s. video.
> 
> Not as if the original figure was being cited as scientific gospel.
> 
> The last paper out of Netflix, they said it works best to stomp out
> the isochronous behaviour and run in FTP mode as much as possible :).
> (Subject to upper limits on quality and application buffers).  Even
> dumb chunk downloading uses TCP; it's not isochronous in the way
> that's usually used to describe RTP etc.
> 



      reply	other threads:[~2016-09-21 21:10 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
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 [this message]

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=1474492221.058911695@apps.rackspace.com \
    --to=dpreed@reed.com \
    --cc=alan.christopher.jenkins@gmail.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    /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