VOD requirements

Hi

I’m using Wowza Stream Engine for Live Streaming and it works great, i want to provide VoD content and want to find bottlenecks of my servers .

I have some questions about my hardware requirements !

my servers have 2x4core CPU + 32GB RAM , The edge servers pull the content from the origin server

How many VOD concurrent users each Edge server can handle with normal HDD storage?? and how many with SSD? (single bitrate and normal quality)

if the HLS decrease performance of my servers in Live and VOD comparing it to rtmp?

what about time-shift ? how many concurrent users each server can handle with 2 hours ABR time shift over HLS?

Is it important to increase the RAM in VOD and Time-Shift ? does the content catch on RAM?

How can i improve the performance ?

Thanks

Hello there,

As described on the Wowza web page, minimum server specifications should be:

CPU: Single Quad Core, 3.00 GHz or better

RAM: 4GB

Disk: 2 or more in RAID 0 (striping)

Network: 1Gb Ethernet

Make sure your servers are tuned according to this guide:

How to do performance tuning

From there you can utilize the MediaCache and LoadBalancer AddOns:

How to scale video on demand streaming with Media Cache

How to get Dynamic Load Balancing AddOn

At which point you can begin to test the setup using the Load Test Tool:

How to get Flash RTMP Load Test Tool

I hope you find this helpful.

Kind regards,

Salvadore

Yes, HTTP clients do produce slightly more load then RTMP clients, but there is an incredibly small difference which I wouldn’t think should be noticeable.

However, you can modify the way the HTTP clients packetize the stream, hence reducing resources consumed. Take a look at this guide for calculating resources consumed and configuring packetization. There are guides for each player technology:

How to configure Apple HLS packetization (cupertinostreaming)

How to configure Adobe HDS packetization (sanjosestreaming)

How to configure Microsoft Smooth Streaming packetization (smoothstreaming)

How to configure MPEG-DASH packetization (mpegdashstreaming)

The …MaxChunkCount is the total number of chunks that are maintained. So as the stream moves a bit further off of live, the player will start to request segments from further in the past. Having a larger list of chunks in reserve will insure this does not lead to a missing chunk error. But it also consumes more resources.

I hope this helps.

Kind regards,

Salvadore

Hello there,

As described on the Wowza web page, minimum server specifications should be:

CPU: Single Quad Core, 3.00 GHz or better

RAM: 4GB

Disk: 2 or more in RAID 0 (striping)

Network: 1Gb Ethernet

Make sure your servers are tuned according to this guide:

How to do performance tuning

From there you can utilize the MediaCache and LoadBalancer AddOns:

How to scale video on demand streaming with Media Cache

How to get Dynamic Load Balancing AddOn

At which point you can begin to test the setup using the Load Test Tool:

How to get Flash RTMP Load Test Tool

I hope you find this helpful.

Kind regards,

Salvadore

Thanks for your reply

I had used all of the links you said and my disks are raid 5

for example in live streaming my server can handle 3000 concurrent users over rtmp ,but in HLS 2hour time shift it can only handle about 400 concurrent users and sometimes more than it wowza service will stop or my disk or server become so slow

does HLS in live streaming use more resources than rtmp ?

I want to know is it normal or I have missed something in my configuration to improve the performance?

Yes, HTTP clients do produce slightly more load then RTMP clients, but there is an incredibly small difference which I wouldn’t think should be noticeable.

However, you can modify the way the HTTP clients packetize the stream, hence reducing resources consumed. Take a look at this guide for calculating resources consumed and configuring packetization. There are guides for each player technology:

How to configure Apple HLS packetization (cupertinostreaming)

How to configure Adobe HDS packetization (sanjosestreaming)

How to configure Microsoft Smooth Streaming packetization (smoothstreaming)

How to configure MPEG-DASH packetization (mpegdashstreaming)

The …MaxChunkCount is the total number of chunks that are maintained. So as the stream moves a bit further off of live, the player will start to request segments from further in the past. Having a larger list of chunks in reserve will insure this does not lead to a missing chunk error. But it also consumes more resources.

I hope this helps.

Kind regards,

Salvadore

i think so . hâhha