[147499] in North American Network Operators' Group
Re: Overall Netflix bandwidth usage numbers on a network?
daemon@ATHENA.MIT.EDU (Patrick W. Gilmore)
Mon Dec 12 15:11:19 2011
From: "Patrick W. Gilmore" <patrick@ianai.net>
In-Reply-To: <4EE58E8E.8000804@bogus.com>
Date: Mon, 12 Dec 2011 15:10:20 -0500
To: NANOG list <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
On Dec 12, 2011, at 12:18 AM, Joel jaeggli wrote:
> On 12/11/11 19:49 , Christopher Morrow wrote:
>> On Sun, Dec 11, 2011 at 10:46 PM, Faisal Imtiaz =
<faisal@snappydsl.net> wrote:
>>> Simple, keep traffic off paid ip transit circuits....
>>>=20
>> (I think joel's point was: "peer with amazon, done-and-done")
>=20
> also probably your relationships to akamai and level3
Netflix's EC2 instances do not speak to end users AFAIK. I believe =
Akamai, LLNW, & L3 are the only companies that stream movies for =
Netflix. Peer with the CDNs to save your transit.
Happy to be educated otherwise if someone knows more than I do.
Netflix's client is also _very_ intelligent. If a user cannot get high =
enough quality from CDN_1, it will switch to CDN_2 without interrupting =
the stream. Which is nice if you have good connectivity to one but not =
the other CDN. (Note I spoke of "good", not "inexpensive" connectivity. =
The NF client doesn't know how much it costs you to show a video, only =
whether there is packet loss.)
--=20
TTFN,
patrick
>>> Faisal
>>>=20
>>> On Dec 11, 2011, at 10:21 PM, Joel Jaeggli <joelja@bogus.com> wrote:
>>>=20
>>>> Netflix uses CDNs for content delivery and the platform runs in =
EC2. What would peering with them achieve?
>>>>=20
>>>> Sent from my iPhone
>>>>=20
>>>> On Dec 11, 2011, at 18:06, Faisal Imtiaz <faisal@snappydsl.net> =
wrote:
>>>>=20
>>>>> Which leads to a question to be asked...
>>>>>=20
>>>>> Is netflix willing to peer directly with ISP / NSP's ?
>>>>>=20
>>>>> Regards.
>>>>>=20
>>>>> Faisal Imtiaz
>>>>> Snappy Internet& Telecom
>>>>>=20
>>>>>=20
>>>>> On 12/11/2011 7:29 PM, Dave Temkin wrote:
>>>>>> Feel free to contact peering@netflix<dot>com - we're happy to =
provide you with delivery statistics for traffic terminating on your =
network.
>>>>>>=20
>>>>>> Regards,
>>>>>> -Dave Temkin
>>>>>> Netflix
>>>>>>=20
>>>>>> On 12/7/11 8:57 AM, Blake Hudson wrote:
>>>>>>> Yeah, that's an interesting one. We currently utilize netflow =
for this, but you also need to consider that netflix streaming is just =
port 80 www traffic. Because netflix uses CDNs, its difficult to pin =
down the traffic to specific hosts in the CDN and say that this traffic =
was netflix, while this traffic was the latest windows update (remember =
this is often a shared hosting platform). We've done our own testing and =
have come to a good solution which uses a combination of nbar, packet =
marking, and netflow to come to a conclusion. On a ~160Mbps link, =
netflix peaks out between 30-50Mbps around 8-10PM each evening. The rest =
of the traffic is predominantly other forms of HTTP traffic (including =
other video streaming services).
>>>>>>>=20
>>>>>>>=20
>>>>>>> Martin Hepworth wrote the following on 12/3/2011 2:36 AM:
>>>>>>>> Also checkout Adrian Cockcroft presentations on their =
architecture which
>>>>>>>> describes how they use aws and CDns etc
>>>>>>>>=20
>>>>>>>> Martin
>>>>>>>>=20
>>>>>>>>=20
>>>>>>>=20
>>>>>>=20
>>>>>>=20
>>>>>>=20
>>>>>=20
>>>>=20
>>>=20
>>=20
>=20
>=20
