VICIfast
ENES
Guides & tutorials

How much CPU each call takes in VICIdial

About 2 cores of fixed load plus 0.03 cores per concurrent call, by our estimates from a measured live floor. How to use that rule, and where it stops helping.

VICIfast Support
··3 min read
Servers in a data centre — illustration for: How much CPU each call takes in VICIdial
Photo by panumas nikhomkhai on Pexels

You're buying or resizing a VICIdial server, and you need to know how many cores to pay for. Your agent count won't tell you. The processor works per call, so that's where our estimate starts.

The rule: 2 cores, plus 0.03 per call

By our estimates, a VICIdial machine needs about 2 cores of fixed load plus 0.03 cores for each of its Concurrent calls (calls up at the same moment). The fixed part is the cost of running VICIdial at all, before the floor gets busy. The per-call part is the one that grows with you.

Three hundredths of a core is nothing for one call. A hundred calls is 3 cores, on top of the fixed 2. Here's how it adds up before any adjustment:

Concurrent callsFixed loadPer-call loadEstimate
502 cores1.5 coresabout 3.5 cores
1002 cores3 coresabout 5 cores
1662 cores5 coresabout 7 cores
3002 cores9 coresabout 11 cores

We adjust both parts for each processor, since a core on one chip isn't a core on another. Treat the table as a starting point, not a promise.

Where the number comes from

We didn't pull it from a spec sheet. We sampled one outbound floor on a 16-vCPU server every five minutes for a full shift: 92 samples with calls up. The floor ran 166 calls, 17 agents and 365 Channel legs (each connected call uses more than one).

Asterisk, the phone engine that places and bridges the calls, used 4.3 cores. MariaDB, the database, used 1.3. The whole machine used about 7.5. The rule says about 7 for 166 calls, close to what the floor really burned. The full shift is written up in what 166 live calls cost a VICIdial server.

Look at the ratio, too: nearly ten calls up for every agent. An outbound floor using Predictive dialing dials ahead of its agents, so at any moment most of those calls haven't reached an agent yet. Size that floor by agents alone and you'd miss most of the load.

Asterisk does most of the work, but the database grows with every call as well. That floor ran 2,230 database queries a second.

What the rule doesn't count

Cores are one limit of several. Dialers also host the agents' phones and the conferences behind every Three-way call, so in a cluster we size them by calls or agents, whichever needs more: one dialer per 300 concurrent calls or 25 agents, and never fewer than two. Our post on how many dialers a cluster needs shows the count.

There's also a ceiling per machine. By our estimates, one machine carries about 600 concurrent calls with room to spare; beyond that, calls belong on dialers of their own. Our guide to VICIdial clusters explains how that split works.

A calm CPU graph with hanging agent screens isn't a core problem. VICIdial's call records sit in tables that lock while a read runs, and a locked table makes the queries behind it wait no matter how many cores sit idle.

Sizing your own floor with it

  • Find the most calls you have up at once on a busy day, not the daily average. Our post on what "most concurrent calls" tells you shows where to read it.
  • Multiply that number by 0.03 and add 2. That's your rough core count.
  • Compare it with what your server has, and check how the processor behaves on a real shift. Our guide to safe CPU and load thresholds covers what "too busy" looks like.
  • If the answer is heading toward 600 calls, plan for a cluster, not a bigger box.

On a small server the fixed 2 cores weigh the most. On a 4-core machine, roughly half the processor is spoken for before the floor gets going, which is why small servers run out of room sooner than the call count suggests.

If your number fits one machine, pick a server size from our plans. If it doesn't, put your numbers into the live cluster sizer for today's price.

Frequently asked

› Does a call to an agent cost more CPU than a ringing call?
Our estimate doesn't split them. It counts every concurrent call the same and was built from a real outbound floor, where most calls up at any moment had not reached an agent yet.
› Why does the database need so few cores?
Asterisk does most of the work on a VICIdial floor. On the floor we measured, the database used 1.3 cores to Asterisk's 4.3, even at 2,230 queries a second.

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. “How much CPU each call takes in VICIdial”. VICIfast LLC, November 20, 2026. Retrieved from https://vicifast.com/blog/vicidial-cpu-per-concurrent-call

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.