vicidial.org

Hi Gurus,

I'm looking into scaling Vicidial and the first thing that I want to know is what is the limit of calls that asterisk can take in vicidial. I am using the performance_test.txt that mflorell wrote in the vicidial docs using SIP protocol ( controller + test server).

I would like to know what is the maximum concurrent calls that you can get in all your vicidial setup? By asking this, we can all see how much others can get and help each other to scale it well.

Kindly state your infrastructure (single server / multi tenant).

In my case:
single server (web+db+asterisk)
512mb ram
Intel Xeon 2.00 Ghz
1 CPU core
* i can reach up to 130 concurrent calls without crash.

I hope that others will also post here the stats that they can get.


Thanks!

Hello,
How many agents logged in?
Inbound , outbound or blended?
What dial ratio?

@ommarrodriguezt. This is outbound only.. it's a performance test. no agents login. I wanna compare my result with others. how about you? how many maximum calls can you take and how many agents are logged in? i forgot to mention. I'm using g711 ulaw codec.

Hello,
We are using G711 codec too.
Maximum calls 125.
1 Server
Quaqcore 2.2 GHZ
4 GB Ram
7.2 K RPM
25 Agents Logged in production

By the way, you can find more info about scalability here: http://download.vicidial.com/iso/vicibo ... nstall.pdf

Below are some examples of dimensioning for various agent loads:
50 Agents Outbound 4:1
• Optional Hardware Specification for Database/Web
• Two Telephony Servers - Standard or Optional specification
75 Agent Outbound 4:1
• Standard Database specification
• One Web server – Standard or Optional specification
• Three Telephony servers - Standard or Optional specification
100 Agent Outbound 4:1
• Standard Database specification
• One Web server – Standard or Optional specification
• Four Telephony servers - Standard or Optional specification
200 Agent Outbound 4:1
• 300-agent Database specification
• Two Web servers – Standard or Optional specification
• Eight Telephony servers - Standard or Optional specification
• Optionally one Web server to act as login load balancer and administration – Standard or
Optional Specification

"concurrent calls" = live calls? or ringing calls? (no sound! which is most of the bandwidth/cpu!)

if (for instance) you have AMD and/or Recording calls active this has a huge effect on call volume capacity. AMD calls are "live" and also using a fairly heft agi script but do not have an agent/meetme room. Ringing calls are completely different because they do not require the infrastructure of the sound system nor the bandwidth of transmitting the sound. So those may not really be "calls" per se.

Then comes the OS and Vicidial version and Installer. All of which have a bearing on system capacity. A "tweaked" Gentoo with no extras in the kernel will react quite differently than a generic Ubuntu with all drivers loaded (even for devices not present or used).

So you may want to format your "my system performs this way" in a spreadsheet design to allow for all of these.

Oh: And HD speed and data transfer rate. 5K rpm laptop drives vs 7.2K rpm SATA cheap drives vs 15K rpm SAS and/or SSD 6g/sec drives can seriously affect throughput and performance. For instance a 72G 15k SAS drive with 6G throughput will allow much more power than a 7200rpm 2T SATA drive. But it won't store all the calls that it generates. LOL