What hardware a VICIdial database server really needs
Every dialer depends on the database machine, yet it needs fewer cores than most people buy. What we measured, the machine we use, and what no hardware can fix.
The database is the one machine in a VICIdial cluster that every dialer and every agent screen depends on, so it's tempting to buy the biggest box on the price list. Before you do, it helps to know what that machine actually spends its time on.
We've measured it twice: on a live floor, and on a replay of the same floor pushed far past its real size. The database itself needs fewer cores than you'd guess. The slowdowns that hurt a floor come from a place hardware can't reach.
How much processor the database uses
On a live outbound floor with 166 Concurrent calls (calls up at the same moment), MariaDB used 1.3 cores while answering 2,230 queries a second. That covers the floor's lookups, call records and status changes.
Then we replayed that floor's real database traffic at seven times its speed, roughly the load of 1,260 calls. The database never needed more than 3.1 of its 16 cores.
So if you're choosing between two processors for this role, raw core count for MariaDB is not what should decide it.
Why the machine still has 16 cores
In our layout the database machine has a second job. The same machine serves the VICIdial admin, the reports and every agent's screen, and each agent screen asks the server for news every second. On one floor, that agent-screen polling was 87.5% of all web requests.
So the cores aren't there for MariaDB alone. They're there so a manager pulling a report and a full floor of refreshing agent screens don't fight the database for the same processor. If you're still on one box, running the VICIdial database on its own server covers the first step of that split.
Here's what we use for the database and its standby, with a dialer alongside for comparison:
| Role | Processor | Cores | Memory | Disks |
| Database + web, and standby | AMD Ryzen 9 7950X3D | 16 cores / 32 threads | 128 GB | 2 x 1.92 TB NVMe, mirrored |
| Dialer | Intel Core i5-13500 | 14 cores (6P + 8E) | 64 GB | 2 x 512 GB NVMe |
The database's two disks are mirrored: every write lands on both, so one failed drive doesn't take the database down with it.
What no hardware fixes
VICIdial keeps its call records in MyISAM tables, which lock the whole table while a read runs. When a report, stats tool or lead search reads the call log for a few seconds, every Disposition (the status an agent picks when a call ends) waits behind it.
On a 60-agent floor, one day-long count held up to 334 statements for as long as 4 seconds. In our replay, the slowest queries at high load came from these locks too, not the processor.
What does help is keeping the busy tables small and the floor's path clear:
- Archive old log rows on a schedule. VICIdial ships a log-archiving script, ADMIN_archive_log_tables.pl, that moves old rows out. A smaller call log means shorter reads, and shorter reads mean shorter locks.
- Switch off campaigns nobody dials. An idle Campaign (a set of leads and dialing rules) left active with a large Hopper (the queue of leads lined up to dial) still works the database. On one floor, idle campaigns were 41% of all database time.
- Keep heavy reads off the shift. We find what holds the call tables during a shift and take it off the floor's path. Our post on why slow reports can stall the whole system shows how to find yours.
Buying it
Buy the database machine for headroom and for its second job, mirror its disks, and give it a twin as the standby. Then spend your attention on the tables, not the processor.
To see where this machine sits among the others, start with the cluster guide. If one server still covers your floor, a single-server plan is the simpler start. When it doesn't, book a sizing call and we'll lay out the machines for your numbers.
Related from VICIfast
- VICIdial cluster sizing, with real numbersA database, dialers and a standby, sized from load we measured on a live floor.
- Bare metal VICIdial serversEvery core yours, mirrored NVMe, delivered in minutes to days. Priced from live stock.
- Work out how many agents a list needsDial ratio, connect rate, and talk time turned into headcount.
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 hardware a VICIdial database server really needs”. VICIfast LLC, November 19, 2026. Retrieved from https://vicifast.com/blog/vicidial-database-server-hardware
Have questions?
Related posts
You might be interested in
VICIfast newsletter
Liked this? Get the next one in your inbox.
We ship the kind of stuff you just read - concrete, numbers-first, no drip. One email when a new post goes live. Unsubscribe in one click.
Comments
No comments yet - be the first.



