# Scalability and other questions with Erizo

**URL:** https://discourse.lynckia.com/t/scalability-and-other-questions-with-erizo/267
**Category:** Uncategorized
**Created:** [May 14, 2014, 10:08am UTC](https://discourse.lynckia.com/t/scalability-and-other-questions-with-erizo/267 "2014-05-14T10:08:47Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![Francois\_Temasys](https://avatars.discourse-cdn.com/v4/letter/f/dfb087/32.png) [@Francois\_Temasys](https://discourse.lynckia.com/u/Francois_Temasys)
#### Post date: [May 14, 2014, 10:08am UTC](https://discourse.lynckia.com/t/scalability-and-other-questions-with-erizo/267/1 "2014-05-14T10:08:47Z")

</div>

Hi,

You may have understood that I’m recently trying to use erizo MCU.  
Unfortunately using either the erizoMCU directly (with my own signaling) or  
using the full installation both ran into errors. I would really appreciate  
help on how to solve them.  
I have been interested to test some parameters using the MCU:

- CPU performances on the client side. Should I expect a gain using the MCU?
- CPU/Memory performances on the server side. What is for you the maximum  
number of client the server can handle at the same time? Under what  
scenario?
- Scalability of the MCU. If you would have to handle 1 000 000 of user I  
believe you would distribute the load on more than one MCU. Although on the  
documentation I don’t see this scenario being considered. What would be  
your approach in this case?
- What is your evaluation of the stability of the MCU currently?

Best regards,  
Francois

---

<div class="post-metadata">

### Author: ![Philipp](https://avatars.discourse-cdn.com/v4/letter/p/46a35a/32.png) [@Philipp](https://discourse.lynckia.com/u/Philipp)
#### Post date: [May 16, 2014, 6:43am UTC](https://discourse.lynckia.com/t/scalability-and-other-questions-with-erizo/267/2 "2014-05-16T06:43:56Z")

</div>

I try to answer my best, IMHO.

- CPU performances on the client side. Should I expect a gain using the MCU?  
No, I don’t think so. Why should there be a gain. CPU intensive tasks are  
transcoding, rendering your webcam in html, etc.

- CPU/Memory performances on the server side. What is for you the maximum  
number of client the server can handle at the same time? Under what  
scenario?  
Erizo is not doing any cpu intensive-tasks, as long there is no  
transcoding, etc. You probably reach your bandwidth limit before.  
We have about 50 KB/s for a single stream. If you have 200 viewers you will  
need an upstream about 10 MB/s. So 100 Mbit connection should be able to  
handle 200 connections.

- Scalability of the MCU.  
Sorry I don’t know a lot of the idea and architecture how erizo will be  
able to scale.  
I guess a second erizo contoller reattaches an existing stream.

- What is your evaluation of the stability of the MCU currently?  
The project recently had some major bug fixes. Unfortunately sometimes we  
hit this crash on different servers:  
[Issues · lynckia/licode · GitHub](https://github.com/ging/licode/issues/114On) Wednesday, May 14, 2014 12:08:47 PM UTC+2, Francois Temasys wrote:

> Hi,
> 
> You may have understood that I’m recently trying to use erizo MCU.  
> Unfortunately using either the erizoMCU directly (with my own signaling) or  
> using the full installation both ran into errors. I would really appreciate  
> help on how to solve them.  
> I have been interested to test some parameters using the MCU:
> 
> - CPU performances on the client side. Should I expect a gain using the  
> MCU?
> - CPU/Memory performances on the server side. What is for you the maximum  
> number of client the server can handle at the same time? Under what  
> scenario?
> - Scalability of the MCU. If you would have to handle 1 000 000 of user I  
> believe you would distribute the load on more than one MCU. Although on the  
> documentation I don’t see this scenario being considered. What would be  
> your approach in this case?
> - What is your evaluation of the stability of the MCU currently?
> 
> Best regards,  
> Francois

---

<div class="post-metadata">

### Author: ![Francois\_Temasys](https://avatars.discourse-cdn.com/v4/letter/f/dfb087/32.png) [@Francois\_Temasys](https://discourse.lynckia.com/u/Francois_Temasys)
#### Post date: [May 26, 2014, 6:23am UTC](https://discourse.lynckia.com/t/scalability-and-other-questions-with-erizo/267/3 "2014-05-26T06:23:32Z")

</div>

Thanks for the answersOn Friday, May 16, 2014 2:43:56 PM UTC+8, Philipp wrote:

> I try to answer my best, IMHO.
> 
> - CPU performances on the client side. Should I expect a gain using the  
> MCU?  
> No, I don’t think so. Why should there be a gain. CPU intensive tasks are  
> transcoding, rendering your webcam in html, etc.
> 
> - CPU/Memory performances on the server side. What is for you the maximum  
> number of client the server can handle at the same time? Under what  
> scenario?  
> Erizo is not doing any cpu intensive-tasks, as long there is no  
> transcoding, etc. You probably reach your bandwidth limit before.  
> We have about 50 KB/s for a single stream. If you have 200 viewers you  
> will need an upstream about 10 MB/s. So 100 Mbit connection should be able  
> to handle 200 connections.
> 
> - Scalability of the MCU.  
> Sorry I don’t know a lot of the idea and architecture how erizo will be  
> able to scale.  
> I guess a second erizo contoller reattaches an existing stream.
> 
> - What is your evaluation of the stability of the MCU currently?  
> The project recently had some major bug fixes. Unfortunately sometimes we  
> hit this crash on different servers:  
> [ErizoController 1 in X.X.X.X does not respond. Deleting it. · Issue #114 · lynckia/licode · GitHub](https://github.com/ging/licode/issues/114)
> 
> On Wednesday, May 14, 2014 12:08:47 PM UTC+2, Francois Temasys wrote:
> 
> > Hi,
> > 
> > You may have understood that I’m recently trying to use erizo MCU.  
> > Unfortunately using either the erizoMCU directly (with my own signaling) or  
> > using the full installation both ran into errors. I would really appreciate  
> > help on how to solve them.  
> > I have been interested to test some parameters using the MCU:
> > 
> > - CPU performances on the client side. Should I expect a gain using the  
> > MCU?
> > - CPU/Memory performances on the server side. What is for you the maximum  
> > number of client the server can handle at the same time? Under what  
> > scenario?
> > - Scalability of the MCU. If you would have to handle 1 000 000 of user I  
> > believe you would distribute the load on more than one MCU. Although on the  
> > documentation I don’t see this scenario being considered. What would be  
> > your approach in this case?
> > - What is your evaluation of the stability of the MCU currently?
> > 
> > Best regards,  
> > Francois
