VICIfast
Guides & tutorials

What 166 live calls cost a VICIdial server: one measured shift

We measured a full outbound shift on one 16-vCPU VICIdial server: 166 calls, 17 agents, about 7.5 cores. Where that load went, and the sizing rule it gave us.

VICIfast Support
··4 min read
What 166 live calls cost a VICIdial server: one measured shift

You know how many agents you have. What you probably don't know is how many cores a real shift burns, because most sizing advice hands you a range instead of a measurement.

So here is a measurement. On 14 October 2026 we watched an outbound floor on one of our 16-vCPU servers for a full shift and took 92 five-minute samples while calls were up. Below is what the server spent, where it went, and the rule we turned it into.

The floor we measured

One outbound floor, one server, one full shift. Averaged over the samples with calls up, it looked like this:

  • 166 Concurrent calls, meaning calls up at the same moment, ringing or talking.
  • 17 agents logged in.
  • 365 channels open in the phone engine.
  • 2,230 database queries a second.
  • About 7.5 cores busy in total.

Two of those numbers surprise people. The first is 166 calls for 17 agents. One agent talks to one customer, so at any moment no more than 17 of those calls could have an agent on them. The rest were still ringing or being connected.

That is normal for an outbound floor running a high Auto dial level (how many lines the dialer opens for each waiting agent). It is also why agent count on its own is a poor way to size a server. Two floors with the same headcount can dial very differently.

The second is 365 channels for 166 calls. A Channel is one leg of a call inside the phone engine, and a single call can use more than one. Here it came to a little over two per call. If you plan in channels, our post on how many Asterisk channels one server can carry picks up from there.

Where the cores went

Asterisk, the phone engine that places and answers every call and hosts the agents' phones, used 4.3 cores. That's the biggest single share: on a VICIdial floor, Asterisk does most of the work.

MariaDB, the database that holds every lead, campaign and call record, used 1.3 cores while answering those 2,230 queries a second. It's the smaller share, but it isn't flat. Every call is logged and updated through the database, and every answered call is handed to an agent through it, so its load climbs with the floor too.

The remaining two cores or so went to everything else a single server runs, from the web pages agents work in to VICIdial's own background processes.

On one server, Asterisk and MariaDB share the same cores. A heavy report or a big list load takes processor time away from the calls while it runs, and the floor slows down with it.

Turning one shift into a sizing rule

One shift isn't a law of nature, but it is a solid place to start. Our per-machine estimates scale from this floor: about 2 cores of fixed load, plus 0.03 cores for every concurrent call.

Check it against the shift itself. Two cores plus 166 times 0.03 comes to about 7 cores, close to the 7.5 we measured. Push the same floor to 300 calls on the same kind of processor and the rule says about 11 cores. That still fits a 16-vCPU server, with less room left for a heavy report at a bad moment.

One caveat: a core on one processor isn't a core on another, so we adjust the per-call figure for each processor we use. Treat 0.03 as the shape of the curve, not a constant. To check your own box against real thresholds, see safe CPU and load levels for a VICIdial server.

When the numbers say one server isn't enough

By our estimates one machine carries about 600 concurrent calls with room to spare. Past that, calls belong on dialers of their own, and the database belongs on a machine that isn't also running Asterisk.

Plenty of floors never get close. If yours lives around 166 calls, one well-sized server does the job, and you can start on a plan without thinking about clusters at all.

If you're nearer the line, read the five signs a floor has outgrown one server, then how the load splits across a cluster. When you want numbers for your own floor, size your cluster and see today's prices.

About VICIfast

We run VICIdial servers for call centres, so you don’t have to. You get the dialer set up, secured and kept running — we handle the server, the updates and the backups. Bring your own phone carrier at no markup, or use VICIfast Voice, our own US calling and numbers, from $0.0085 a minute. From $49 a month per server.

Questions? Call +1 636 556 0022 and talk to someone who runs dialers.

Citing this article

VICIfast Engineering. “What 166 live calls cost a VICIdial server: one measured shift”. VICIfast LLC, November 19, 2026. Retrieved from https://vicifast.com/blog/measured-vicidial-floor-166-calls

Have questions?

Related posts

You might be interested in

Comments

Comments are reviewed before they appear. We never publish your email.

No comments yet - be the first.