SIZING

[hanidhakwani]

Hello,
I currently have:
- 1 DB / Web server with 32G RAM + Intel (R) Xeon (R) CPU D-1531 @ 2.20GHz (12 C) + 2x250G SSD (RAID 0 SOFT)
- - 1 ASTERISK server with 32G RAM + Intel (R) Xeon (R) CPU D-1531 @ 2.20GHz (12 C) + 2x250G SSD (RAID 0 SOFT)
What is the maximum number of agents that can hardly support with outbound predictive campaigns?
Thank you

[williamconley]

agent count is only one factor. And the only way to be certain is to TEST. Number of outbound and inbound calls, each of which fires up its own agi scripts. Recording calls, codec in use, reports being run, real time screens in use. Everything happening on the server takes up CPU and RAM and network bandwidth.

Test.

Otherwise, the best way to guess is to use the specifications in the Vicidial Manager's Manual. Free downloadable manual on EFLO.net.

[hanidhakwani]

Is there a sizing calculator?
I give you estimates on usage:
- agent number: 150
- outgoing call: between 600 and 1500 (depending on the campaign)
- recording: all
-code: alaw
- real time: 10
with the current configuration is it possible to support this number of agents, or do I have to add other servers?
thank you

[carpenox]

youll be fine

[williamconley]

the best way to guess is to use the specifications in the Vicidial Manager's Manual. Free downloadable manual on EFLO.net.

Anybody who says anything requiring less hardware than what the Manager's Manual suggests ... has probably never dealt with an enterprise-level system (or perhaps only ONE). Individual servers are difficult to predict even with full knowledge of the scenario, but a cluster with 150 agents and 1500 calls? Not predictable.

Make sure you have at least two servers for every role. With 150 agents, you should be looking at 4 dialers minimum.

Note that "DB" and "Replication/Reporting" are both database servers, so while technically there can be only one DB server, since the DB is also loaded into the replication server, which is used to generate reports without interfering with operations, I consider it similar enough to call it the second DB server.