Ant Media Server costs calculation considerations for 1-1 peering style architecture

[Mike Shackleford]

Using the And Media cost calculator (https://antmedia.io/cost-calculator/) and referring to the section on "standalone" server estimates towards the bottom of the page, the table indicates that:

   A c2-standard-16 (in Google Compute Engine terms, 16 vCPU) can handle ~200 concurrent publishers. 

Our model is a 1 <-- --> 1 WebRTC peering model where for every (1) broadcast there will be (1) viewer. Think of a "Doorbell cam" or "Baby Monitor" type product design. In most cases, Ant Media will serve as a signaling server, except for those cases where we cannot create a direct peer <--> peer connection and must pass bytes through the cloud (either through Ant or through Coturn). There's no expectation for server side recording or adaptive bitrates. 

My question is, given that in ~80% of the cases (we hope) Ant will only act as a signaling server and not relay the audio/video or do any transcoding, does that alter the estimate? My expectation would be that Ant could handle higher numbers of "publisher/subscriber" pairs if the audio and video are not being sent through the cloud or transcoded, but I'm not sure. 

Is there any guidance on that, or will I have to wait until I can set up a proper load testing environment with the tooling provided? Thanks for any help. 

[Mohit]

19 hours ago, Mike Shackleford said:

Using the And Media cost calculator (https://antmedia.io/cost-calculator/) and referring to the section on "standalone" server estimates towards the bottom of the page, the table indicates that:

   A c2-standard-16 (in Google Compute Engine terms, 16 vCPU) can handle ~200 concurrent publishers. 

Our model is a 1 <-- --> 1 WebRTC peering model where for every (1) broadcast there will be (1) viewer. Think of a "Doorbell cam" or "Baby Monitor" type product design. In most cases, Ant Media will serve as a signaling server, except for those cases where we cannot create a direct peer <--> peer connection and must pass bytes through the cloud (either through Ant or through Coturn). There's no expectation for server side recording or adaptive bitrates. 

My question is, given that in ~80% of the cases (we hope) Ant will only act as a signaling server and not relay the audio/video or do any transcoding, does that alter the estimate? My expectation would be that Ant could handle higher numbers of "publisher/subscriber" pairs if the audio and video are not being sent through the cloud or transcoded, but I'm not sure. 

Is there any guidance on that, or will I have to wait until I can set up a proper load testing environment with the tooling provided? Thanks for any help. 

Hi Mike,

How are you?

Thank you for explaining your use case in detail.

Yes you are right since in your use case it's just being used a signalling server and not for transmitting the audio and video data it can support a large number of streams maybe in thousands.

 

Reagrds,

Mohit Dubey 

[Mike Shackleford]

Thank you so much for the prompt response. I will of course use load testing to verify and scale our project appropriately, but this information is very helpful. 

[Connessione]

On 7/1/2022 at 2:24 AM, Mike Shackleford said:

Using the And Media cost calculator (https://antmedia.io/cost-calculator/) and referring to the section on "standalone" server estimates towards the bottom of the page, the table indicates that:

   A c2-standard-16 (in Google Compute Engine terms, 16 vCPU) can handle ~200 concurrent publishers. 

Our model is a 1 <-- --> 1 WebRTC peering model where for every (1) broadcast there will be (1) viewer. Think of a "Doorbell cam" or "Baby Monitor" type product design. In most cases, Ant Media will serve as a signaling server, except for those cases where we cannot create a direct peer <--> peer connection and must pass bytes through the cloud (either through Ant or through Coturn). There's no expectation for server side recording or adaptive bitrates. 

My question is, given that in ~80% of the cases (we hope) Ant will only act as a signaling server and not relay the audio/video or do any transcoding, does that alter the estimate? My expectation would be that Ant could handle higher numbers of "publisher/subscriber" pairs if the audio and video are not being sent through the cloud or transcoded, but I'm not sure. 

Is there any guidance on that, or will I have to wait until I can set up a proper load testing environment with the tooling provided? Thanks for any help. 

 

[Connessione]

You can also consider using something like nodejs along side rest of the system when it comes to just signalling using websockets or so. For anything other than one to one use AMS.that will be a more efficient structure.