How do we scale to an unlimited number of conference rooms (16 (max users) in seperate video chats)

[Zale Schoenborn]

You document how to scale broadcast but not the # of conference rooms.

 

Any guidance or best practices on how this can scale conference rooms on AMI is super helpful as we have lots of questions and concerns to follow a scale pattern you've tested and proven works.

 

Here's a couple questions we have but please add any additional detail you think is relevant...

 

We noticed your reference html conference app does not use separate edge and origin nodes to play and publish respectively. Do you recommend we use the same origins and edge concept used in scaling broadcasting to scale to an unlimited number of 16 person video chat rooms. 

 

Can this unlimited number chats live in one application or do we need to split the chat groups up somehow into multiple applications?

 

 

 

[Connessione]

Until MCU becomes available, true conference scaling is a myth. One of the practical ways to scale conferences is to have multiple servers and each conference should reserve slots on a server (origin) if available. Standard existing clustering can probably also be used, but I don’t think that is a good option because I of latency etc.

Multiple applications/ multiple rooms are the same thing. They are like hard disk partitions. They ultimately use same resources.

 

[Ant Media Support]

Hi Zale Schoenborn,
Hope you are fine.
Thanks for reaching out to Ant Media.

​
When you configure the load balancer, you send everything to load balancer URL and it is then distributed to edge and origin, that is why the origin and edge server is not separated in the conference app.
For a conference call you have n publisher and n*(n-1) viewers. So as per 16 person conference there will be 16 x (16-1)= 240 viewers

For estimating your requirements you can take a look at our cost calculator

https://antmedia.io/cost-calculator/

 

Regards,
Yash

Star Ant Media Server on GitHub and get a chance to win an AMS Annual Enterprise Edition License.

On Wed, 16 Jun at 6:28 PM , Zale Schoenborn <zale@frqncy.live> wrote:

You document how to scale broadcast but not the # of conference rooms.

Any guidance or best practices on how this can scale conference rooms on AMI is super helpful as we have lots of questions and concerns to follow a scale pattern you've tested and proven works.

Here's a couple questions we have but please add any additional detail you think is relevant...

We noticed your reference html conference app does not use separate edge and origin nodes to play and publish respectively. Do you recommend we use the same origins and edge concept used in scaling broadcasting to scale to an unlimited number of 16 person video chat rooms. 

Can this unlimited number chats live in one application or do we need to split the chat groups up somehow into multiple applications?

--
You received this message because you are subscribed to the Google Groups "Ant Media Server" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ant-media-server+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ant-media-server/07bb4776-af9d-4059-b410-f3ec48d1ad69n%40googlegroups.com.

43063:1264838

[Zale Schoenborn]

Hi Yash,

Your explanation does not make sense as there are two load balancers is your AMI cluster reference implementation for AWS (one for the origin and one for the edge).

Can you please help clarify?

Also, will adding more and more rooms on an auto scale configuration in AWS work with large number of chat rooms or is there any issues.

Zale

 

Sent from my iPhone

On Jun 21, 2021, at 8:59 AM, Ant Media Support <support@antmedia.io> wrote:

 



Hi Zale Schoenborn,

Hope you are fine.

Thanks for reaching out to Ant Media.

​

When you configure the load balancer, you send everything to load balancer URL and it is then distributed to edge and origin, that is why the origin and edge server is not separated in the conference app.

For a conference call you have n publisher and n*(n-1) viewers. So as per 16 person conference there will be 16 x (16-1)= 240 viewers

For estimating your requirements you can take a look at our cost calculator

https://antmedia.io/cost-calculator/

 

Regards,

Yash

Star Ant Media Server on GitHub and get a chance to win an AMS Annual Enterprise Edition License.

On Wed, 16 Jun at 6:28 PM , Zale Schoenborn <zale@frqncy.live> wrote:

You document how to scale broadcast but not the # of conference rooms.

 

Any guidance or best practices on how this can scale conference rooms on AMI is super helpful as we have lots of questions and concerns to follow a scale pattern you've tested and proven works.

 

Here's a couple questions we have but please add any additional detail you think is relevant...

 

We noticed your reference html conference app does not use separate edge and origin nodes to play and publish respectively. Do you recommend we use the same origins and edge concept used in scaling broadcasting to scale to an unlimited number of 16 person video chat rooms. 

 

Can this unlimited number chats live in one application or do we need to split the chat groups up somehow into multiple applications?

 

 

 

--

You received this message because you are subscribed to the Google Groups "Ant Media Server" group.

To unsubscribe from this group and stop receiving emails from it, send an email to ant-media-server+unsubscribe@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/ant-media-server/07bb4776-af9d-4059-b410-f3ec48d1ad69n%40googlegroups.com.

43063:1264838

[Tahir]

Hi,

There are two load balancers but one of them is for RTMP and the other one is for WebRTC, it is not that one of them is for origin and other one is for edge servers, there must be one load balancer depending on your protocol. 

 

[David Knape]

Yes, but there are two ALB Target groups (origin and edge) assigned to different ports. We must choose one. This answer still does not make sense to us. If you say all conference connections should go to the same group, that makes sense. But, it doesn't sound like there is any origin/edge differentiation happening in this case.

Let's get to the root of it. 

What is the best practice for scaling conference chat? Is anyone else trying to use conference in production, and how are you doing it?

Is the sample AWS cloudformation template designed to work with conference, or just broadcast streams?

Underneath, how does conference functionality work in a clustered environment? If I have 10 people connected to a room and the all end up at different servers in the load balancer group, this does not seem very efficient. I think I agree with "Connessione" above, that this is a myth.

Suggestions welcome.