[147472] in North American Network Operators' Group
Re: Overall Netflix bandwidth usage numbers on a network?
daemon@ATHENA.MIT.EDU (Faisal Imtiaz)
Sun Dec 11 23:42:41 2011
In-Reply-To: <CAL9jLaZpDjH4QTM3Fjx=6gz6s6_z-JArGzJGBa5nEOWtSRErXw@mail.gmail.com>
From: Faisal Imtiaz <faisal@snappydsl.net>
Date: Sun, 11 Dec 2011 23:41:23 -0500
To: Christopher Morrow <morrowc.lists@gmail.com>
Cc: "nanog@nanog.org" <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
Thanks for the explanation...did not consider that before...will investigate=
.., any tips that can be shared will be welcome.
:)
Faisal
On Dec 11, 2011, at 10:49 PM, Christopher Morrow <morrowc.lists@gmail.com> w=
rote:
> On Sun, Dec 11, 2011 at 10:46 PM, Faisal Imtiaz <faisal@snappydsl.net> wro=
te:
>> Simple, keep traffic off paid ip transit circuits....
>>=20
>=20
> (I think joel's point was: "peer with amazon, done-and-done")
>=20
>> 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. Wha=
t 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 y=
ou 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 thi=
s, but you also need to consider that netflix streaming is just port 80 www t=
raffic. Because netflix uses CDNs, its difficult to pin down the traffic to s=
pecific hosts in the CDN and say that this traffic was netflix, while this t=
raffic was the latest windows update (remember this is often a shared hostin=
g platform). We've done our own testing and have come to a good solution whi=
ch uses a combination of nbar, packet marking, and netflow to come to a conc=
lusion. On a ~160Mbps link, netflix peaks out between 30-50Mbps around 8-10P=
M 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 w=
hich
>>>>>>> describes how they use aws and CDns etc
>>>>>>>=20
>>>>>>> Martin
>>>>>>>=20
>>>>>>>=20
>>>>>>=20
>>>>>=20
>>>>>=20
>>>>>=20
>>>>=20
>>>=20
>>=20
>=20
