Page 1 of 2 12 LastLast
Results 1 to 10 of 17

Thread: One VOD application with 200 user subfolders, or 200 applications?

  1. #1

    Default One VOD application with 200 user subfolders, or 200 applications?

    I'm considering to enable VOD streaming for a large number of user accounts, and am wondering if it makes sense to create an application config for each of them, or to just arrange their media folders below /vod

    Just for the cleaner URL starting with the user folder name, I am leaning towards unique applications, plus it would allow me to customize each of them if needed. Is there a downside to having that many applications configured? Server is quite powerful, 16 core, 24GB RAM.

    Peter

  2. #2
    Join Date
    Dec 2007
    Posts
    22,013

    Default

    Peter,

    I would go with separate applications. There isn't a downside. You will probably get a lot of diverse playback, i.e., many playback clients playing many different streams, resulting in heavy disk reads. So you will want a RAID 0 or 1+0 disk array with as many disks as possible, preferably SSD drives.

    Richard

  3. #3

    Default

    The system drive handles the current load just fine (local RAID6, but using enterprise storage via fiberchannel for the main on-demand content). Currently it's all running through FMS 4.5, configured with one application per user account and performance is fine. I was more concerned about memory use or caching issues. I like the separate applications for many reasons, such as easy filtering of logs in Sawmill and the ability to keep the URLs similar to what we have been using.

    Peter

  4. #4

    Default

    In testing this I noticed rather slow startup of videos, as well as significant delays when moving along on the timeline (buffering?). Is htis normal? 16 core server, running 2 transcode jobs in the background for live streams at 30% total CPU load. On demand streams from Wowza can take between 4 and 17 seconds to start playing, and when cueing ahead in the timeline, it can be 4-7 seconds again. Is this normal? Example here

  5. #5
    Join Date
    Dec 2007
    Posts
    22,013

    Default

    The first one does not seem to work. ffprobe says it does not exist.

    The second one starts in about 3 seconds for me, which is default bufferLenght in JW player. Seek is about the same. The encoding looks okay: 24 fps. Sometimes low fps is a factor.

    Richard

  6. #6

    Default

    not sure what you mean by "does not exist" - it plays, but with delay. Right now I had about 5+ seconds delay in Flash. Load the page in iPad and you will wait about 8-15 seconds on the upper player. Unacceptable.

    The second player will also fast forward to any point once you start playing with zero delay (at least here locally) - first player will rebuffer 3+ seconds on the same connection. First player is Wowza, second is FMS source, same server, same source file.
    Last edited by pburke; 05-10-2013 at 08:48 AM.

  7. #7
    Join Date
    Dec 2007
    Posts
    22,013

    Default

    Try setting the "bufferLength" Flashvar to "1" or "0"

    Richard

  8. #8
    Join Date
    Sep 2011
    Posts
    1,920

    Default

    Hi,
    The delay for iOS is due the the design for HTTP streaming.
    The iOS device requires 3 chunks by default before it will play the stream hence the longer delay.
    You can change values using the guide here,
    http://www.wowza.com/forums/content....tinostreaming)

    Note : You are running a on demand application.

    You can control the video on demand (VOD) chunk size by adding the following property to the HTTPStreamer/Properties container:
    <Property>
    	<Name>cupertinoChunkDurationTarget</Name>
    	<Value>10000</Value>
    	<Type>Integer</Type>
    </Property>
    Try changing this value to 2000 and see if it help your streaming situation.

    Jason

  9. #9
    Join Date
    Dec 2007
    Posts
    22,013

    Default

    For the cupertinoChunkDurationTarget, note you have to have know the key frame frequency to set it properly. Wowza will only break chunks on key frames. Looking at the chunklist.m3u8 (portion below) of your stream, your chunks are about 10, 11 seconds long. So your key frame interval is probably either 10 seconds or some factor of 10: 1, 2 or 5. But might be something odd. There is 3 second range from about 9.5 to 12.5 in chunk length. If you have 3 second key frame frequency you would set cupertinoChunkDurationTarget to 9000, 3000 or 1000.

    Can you copy that file to your web server and send link to download it to support@wowza.com. That will open a ticket. Zip up your /conf and /logs folders and include those. Include a link to this thread for reference.

    #EXTINF:10.167,
    media_1.ts?wowzasessionid=631428869
    #EXTINF:11.541,
    media_2.ts?wowzasessionid=631428869
    #EXTINF:9.584,
    media_3.ts?wowzasessionid=631428869
    #EXTINF:11.166,
    media_4.ts?wowzasessionid=631428869
    #EXTINF:11.917,
    media_5.ts?wowzasessionid=631428869
    #EXTINF:12.583,
    media_6.ts?wowzasessionid=631428869
    #EXTINF:9.625,
    media_7.ts?wowzasessionid=631428869
    #EXTINF:12.917,
    media_8.ts?wowzasessionid=631428869
    #EXTINF:12.792,
    media_9.ts?wowzasessionid=631428869
    #EXTINF:9.5,
    media_10.ts?wowzasessionid=631428869
    #EXTINF:11.666,
    media_11.ts?wowzasessionid=631428869
    #EXTINF:11.0,
    media_12.ts?wowzasessionid=631428869
    #EXTINF:11.167,
    media_13.ts?wowzasessionid=631428869
    #EXTINF:11.458,
    media_14.ts?wowzasessionid=631428869
    #EXTINF:9.667,
    media_15.ts?wowzasessionid=631428869
    #EXTINF:11.375,
    media_16.ts?wowzasessionid=631428869
    #EXTINF:11.667,


    Richard

  10. #10

    Default

    Quote Originally Posted by JasonH View Post
    Hi,
    The delay for iOS is due the the design for HTTP streaming.
    The iOS device requires 3 chunks by default before it will play the stream hence the longer delay.
    You can change values using the guide here,
    http://www.wowza.com/forums/content....tinostreaming)

    Note : You are running a on demand application.

    You can control the video on demand (VOD) chunk size by adding the following property to the HTTPStreamer/Properties container:
    <Property>
    	<Name>cupertinoChunkDurationTarget</Name>
    	<Value>10000</Value>
    	<Type>Integer</Type>
    </Property>
    Try changing this value to 2000 and see if it help your streaming situation.

    Jason
    Jason,

    I put in the default 10000 value first - tested it and got a 9 second startup. Then I changed the value to 2000 and the startup took 17 seconds. In previous testing, those were about the range of results I was getting before, so I don't think this has any impact on performance. Fast forwarding is about 9 seconds delay each setting - you see the target key frame, it freezes, and eventually plays.

    Looking at Jconsole, I see 21-25% CPU use, 245 threads, 1.5GB Heap Memory use, rising from 1.3 to 1.8GB and then dropping again hard to 1.25GB every 60-80b seconds. Restarted the Wowza service but no change in playback performance, other than lower heap memory, which seems to run between 500mb and 1GB now. Screenshot of the console overview for the period before and after service restart:



    based on what I am seeing locally, I have a hunch that this may be a network issue. I see 10x the available bandwidth on the FMS server, even though Wowza sits on the 10 gig card, while FMS has 1 gig. Probably something only our network folks can troubleshoot, and since few of us here are using their 10 gig connection, I have a feeling they may have screwed something up and nobody noticed. I can't get more than 2mbps from that server, while I have 97mbps available to the other one.

Page 1 of 2 12 LastLast

Similar Threads

  1. 200 responses for missing SMIL files
    By Snapster in forum General Forum
    Replies: 1
    Last Post: 02-07-2014, 06:53 AM
  2. logs 200 giga
    By vision in forum General Forum
    Replies: 1
    Last Post: 01-06-2014, 02:37 AM
  3. Should i create smil file for each 200 video?
    By kayasey in forum General Forum
    Replies: 6
    Last Post: 07-24-2013, 07:53 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •