Results 1 to 3 of 3

Thread: Live stream chunking through different application

  1. Default Live stream chunking through different application


    we're looking into a solution to get a more stable Wowza setup with multiple servers. We currently have a setup on which all incoming live streams (push from encoders or pulled from off-site origins) are chunked. So our 'live' application has all the LiveStreamPacketizers enabled. The problem with this is, that it takes more system resources, because of the 30 seconds of chunk data that needs to stay in memory for all three LiveStreamPacketizers (iOS/cupertino, Smooth and Zeri/sanjose).

    In order to make it more stable, we have the following idea:
    We are able to relay from one application to another application on the same Wowza server. We want to change the 'live' application in such a way that it does not create chunks anymore. It is only used for RTMP streaming. By creating another application called 'chunker' and enabling the LiveStreamPacketizers there, we can just relay those streams that really need it to the chunker and not all streams. This is done with the StreamNameAlias package and the StreamManager. This should reduce the system resources for that Wowza machine. Less chunking is less memory usage... Is this a correct assumption?

    The second issue is the relaying of the chunks. We are thinking that we could do the same with relays: We relay an RTMP stream from our origin server to an edge server. On that edge server we relay it internally to the chunker application. And that in turn is chunking the stream. However, I think that this will take more resources of the machine than if when we use the LiveStreamPacketizer's repeater option. As I understand it, this will just relay the chunks from the origin to the edge, and not rechunk them on the edge. In other words, creating chunks from a RTMP stream is more resource demanding then relaying the chunks. Is this a correct assumption?

    So to conclude:
    - on our origin server we relay an incoming RTMP stream internally to the chunker application
    - on the edge server we use the LiveStreamPacketizers repeater functionality
    This sounds like the best solution for chunking with Wowza. Is this correct? Or are there other methods of doing this?

    Kind regards

  2. #2
    Join Date
    Dec 2007


    You can easily packetize on the edge instead of the origin by leaving the origin Application.xml /LiveStreamPacketizers empty, and using the regular packetizers in the edge Application.xml /LiveStreamPacketizers

    You reduce latency in HTTP streaming with these segmenter property settings and short key frame frequency.'


  3. Default


    We are looking for a way to reduce the memory usage. Latency is not an issue.

    The problem is that some live streams that are pulled from an external encoder are chunked, even when there is no source. And that gives problems, and a lot of errors. Also when the settings of the RTMP stream are not correct, which happens often, the chunkers are also causing problems. So we are looking in a way that chunking is only done for certain streams. So a different (new) application in Wowza.

    We need to serve the chunks also on the origin server. So there will be chunking earlier in the chain.

    But maybe this is more clear. What takes more memory/cpu? The LiveStreamPacketizers or the LiveStreamPacketizersRepeaters?

    Kind regards,

Similar Threads

  1. Setting up Wowza for HLS chunking and streaming
    By spence in forum General Forum
    Replies: 5
    Last Post: 10-24-2013, 12:07 PM
  2. Stop chunking HLS stream after x retries
    By charly in forum Live Streaming and Encoder Discussion
    Replies: 4
    Last Post: 11-13-2012, 01:16 PM

Posting Permissions

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