Reviews:
 ·Verizon Wireless..
| reply to pandora
Re: Holy cow, Netflix really does use a lot of bandwidth ... Yea, I know when I was watching LOST on Netflix and I was watching 7-8 hours a day... trying to catch up for the next season I was getting a good 10-15 GB consumption per day. Like I said I can see how its possible but you would really have to try is all I'm saying.  |
|
pandoraPremium
join:2001-06-01
Outland
kudos:1 Reviews:
 ·Google Voice
 ·Comcast
·ooma
·Future Nine Corp..
| said by MalibuMaxx:Yea, I know when I was watching LOST on Netflix and I was watching 7-8 hours a day... trying to catch up for the next season I was getting a good 10-15 GB consumption per day. Like I said I can see how its possible but you would really have to try is all I'm saying. Until we have 2, 3 or 4 sets running IPTV. Then it may not be as difficult.
--
"People demand freedom of speech as a compensation for the freedom of thought which they seldom use." |
|
 camperPremium
join:2010-03-21
Bethel, CT
·Comcast
| reply to MalibuMaxx
Another data point. I just finished watching "Outsourced" via Netflix instant streaming. It is an HD movie. I took a snapshot of the traffic at the beginning and the end of the movie. The numbers are:
Date Time Downstream Upstream
Apr 18 13:36:22 4,562,200,162 562,646,050
Apr 18 14:00:01 5,326,113,698 574,868,378
Apr 18 15:00:01 7,120,817,370 604,758,131
Apr 18 15:20:57 7,633,710,744 613,650,259
Looks like about 3.1GB for the hour and 42 minute movie. |
|
 JohnInSJPremium
join:2003-09-22
San Jose, CA
·PHONE POWER
·Comcast
| said by camper:Looks like about 3.1GB for the hour and 42 minute movie. And google calls that...
(3.1 gigabytes) / (102 minutes) = 531.141438 kBps
which is....
((3.1 GB) / (102 minutes)) * (60 minutes) = 1.82352941 gigabytes
Per hour.
Or, pretty much in the old ball park.
--
My place : »www.schettino.us |
|
 ahhnold
join:2003-12-04
Orland Park, IL | reply to camper
said by camper:I took a snapshot of the traffic at the beginning and the end of the movie. The numbers are:
Date Time Downstream Upstream
Apr 18 13:36:22 4,562,200,162 562,646,050
Apr 18 15:20:57 7,633,710,744 613,650,259
That difference is 3072 MBytes.
Using VPC1 HD rate of 3.8 Mbits/Sec, WMA 2.0 Audio Encoder rate of 220 kbits/Sec including protocol overhead sums to an aggregate rate of 4.02 Mbits/sec.
102 minute movie is 6120 seconds in length.
The movie has a total size of:
4.02 Mbits/Sec * 6120 Sec = 24,602 Mbits.
Converting from bits to Bytes:
24,602 Mbits / ( 8 bits / 1 Byte ) = 3075 MBytes or 3.075 GBytes.
So all the math works as expected within an error factor of 1*10^-4
That rate can be generalized to 1809 MBytes/Hour ... for now.
Later this year Netflix is supposed to start streaming multichannel audio which will bump up the audio rate between 250 and 500 kbits/sec. That moves the aggregate rate for an HD movie to 1935 Mbytes/Hour. |
|
|
|
