Skip navigation
NitinChopra
Currently Being Moderated

Severe performance issues while publishing content to be served as live as well as VOD

Dec 19, 2013 3:28 AM

We are facing performance issues (high initial delay, frequent buffering) while trying to stream (HDS/HLS) VOD content recorded through AMS.

 

We have modified the livepkgr server action script (main.asc) to record 2 copies of the content - 1 for live publishing (4 second f4f fragments) and another for recording VOD for entire program duration.

 

For small duration content (less than 30 minutes), HDS streaming is fine through f4fhttp module.

 

When content grows greater than 30 minutes, we start facing problems of delay, buffering. It seems the apache module f4fhttp takes long time to serve f4m as well as f4f fragments for longer content.

 

On analysing the content, it contains metadata stream (amf0) which differentiates this content from regular VOD f4v file which has only video, audio stream.

 

And surprisingly, if we modify the content to remove this amf0 stream, the content plays fine from f4fhttp module. The delay, buffering are gone.

 

My queries are:

 

- Is this a known issue with AMS apache f4fhttp, hlshttp modules that they face performance issues while serving content created through AMS?

- Any way to fix this performance issue or overcome this limitation of AMS apache modules?

 

 

Here is my usecase:

 

- We are currently using AMS on AWS EC2 to publish multi-bitrate live streams (24x7 TV content). Publishing works fine with livepkgr application with default

segment sizes etc.

 

- We also want to be able to store the content (split program-wise) to be able to view as VOD later. For this, we have modified the livepkgr server action script (main.asc) to record 2 copies of the content - 1 for live publishing (4 second f4f fragments) and another for program specific recordings for vod.

 

Both live, vod recordings are created fine.

But we face following performance issues while trying to playback the VOD content with duration more than 30 minutes.

 

In case there is an alternative solution to address our usecase, please inform that as well.

 

Thanks,

Nitin

 

More Like This

  • Retrieving data ...

Bookmarked By (0)

Answers + Points = Status

  • 10 points awarded for Correct Answers
  • 5 points awarded for Helpful Answers
  • 10,000+ points
  • 1,001-10,000 points
  • 501-1,000 points
  • 5-500 points