Answer by Scott Kellicker · Mar 05, 2012 at 02:36 PM
I just switched to nDVR and currently have about 24 hour of nDVR window.
Now, I couldn't help but notice difference in bandwidth consumption.
With RTMP(JW), a 500k live stream consumes just about 500kbps.
With SanJose (Strobe), a 500k live stream consumes about 1mbps average.
With Cuptertino(iOS 5.0.1), a 500k live stream consumes about 4-5mbps average.
I understand that the delivery mechanism is different from RTMP streaming (a burst for each chunk), but shouldn't the usage pattern average out to the stream's bitrate?
What am I missing?
Answer by Richard Lanham · Aug 20, 2012 at 12:38 PM
Answer by Scott Kellicker · Mar 30, 2012 at 06:32 AM
I've noticed the big difference in the bandwidth consumption too when using nDVR. In my case it triples the original stream bitrate. It's due to the periodic playlist requests from the client. Using gzip when sending the playlist could be a solution as it significantly reduces the size of the playlist. According to the HTTP Live Streaming draft RFC (since rfc v.04) the server should support gzip encoding if client request to use it.
As Scott said it's best to keep the playlist short by using APIs but in my case I can't use it as i need to provide instant access to 24h live nDVR stream.
Is there any plan to support gzipped playlist in the near feature?
wowza session id? 0 Answers
My first nDVR playback not working 1 Answer
DVR streamTimeout unexpectedly 1 Answer