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).
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
Martin