Why VICIdial dispositions take seconds to save
When agents pick a status and the screen hangs, the database is usually waiting on a report or search that is reading the call log. How to find it and stop it.

An agent picks a status, clicks submit, and the screen just sits there. A few seconds later it jumps to the next call as if nothing happened. When it's one agent, it's an annoyance. When the whole floor freezes at the same moment, you're paying for dead seconds on every seat.
What a save actually does
A Disposition is the result an agent picks when a call ends: sale, callback, not interested. Saving it is a write to the database. The call record gets its status, the Lead gets updated, and the agent moves on to the next call or a pause.
On a single server that write goes to the same box that runs the calls. On a cluster it goes to the database and web server, the one machine that holds every lead and call record, as the cluster guide explains. Either way, the write itself is tiny. The delay comes from what else is using the same tables at that second.
Why the write has to wait
VICIdial keeps its call records in MyISAM tables. A MyISAM table is locked as a whole while a read runs on it, so no write can land until that read finishes. Your agent's save is one of those writes.
Quick reads cost nothing. The trouble is a read that works through the call log for seconds at a time. While it runs, every save on the floor lines up behind it, and every second they wait is added to each agent's Wrap-up time.
On a 60-agent floor we measured, one day-long count held up to 334 statements for as long as 4 seconds. That's the freeze your agents feel: the screen waits for the database, and the database waits for one report.
flowchart LR
A[Agent clicks submit] --> W[Web server]
W --> T[(Call log table)]
R[Day-long report] -->|reading, table locked| T
T -->|write waits| Q[Saves queue up]
Q -->|report finishes| S[Statuses saved]
S --> N[Agents move on]The usual culprits
- Long reports run mid-shift. A count or export over a whole day reads a lot of call log, and it does it while the floor is busiest.
- Stats tools that never stop reading. Wallboards and stats pages that keep re-reading the call log keep the table busy all shift.
- Lead search by phone number. VICIdial's call log was missing a phone-number index, so a search by phone read the entire log. On one floor that meant dialer freezes of 4 to 12 seconds.
- Log tables nobody archives. The bigger the call log, the longer every read on it takes, and the longer the lock lasts.
The same lock delays the step where VICIdial hands a fresh call to a free agent, so a floor with slow saves often sees its Drop rate climb at the same moments.
Finding the one that's hurting you
Start by watching who freezes. If one agent's saves are slow while everyone else's are fine, check that agent's browser and connection. If the whole floor stalls at the same second and recovers together, something is holding the call tables.
Then find what ran at that moment. The Admin Report Log Viewer lists every report pulled, who ran it, when, and how long it took to compile. Line those times up against when agents complained, and the long-running report usually names itself.
A faster processor won't shorten a lock. When we pushed a real floor's database traffic to seven times its load, the processor wasn't what ran out; the slow moments came from locks on the call log.
What fixes it
- Move day-long reports and exports to before or after the shift.
- Take stats tools off the live call log during the shift, or have them refresh far less often.
- Add the missing phone-number index to the call log. Every cluster we build gets it.
- Archive old log rows on a schedule with VICIdial's log-archiving script, ADMIN_archive_log_tables.pl, so the tables stay small.
If your floor still fits on one machine, these fixes apply there too, and a single-server plan is the simpler place to start. On every cluster we run, we find what holds the call tables during a shift and take it off the floor's path.
Frequently asked
- Rarely. The save is waiting for a lock on the call log, not for the processor. Shorten or move whatever holds the lock.
- Only if that one agent is slow and everyone else is fine. When the whole floor stalls at the same moment, look at the database.
› Will a faster processor or more memory fix slow dispositions?
› Could it just be the agent's internet connection?
When you're ready for a database that has a machine to itself, bring your floor's numbers to a sizing call.
Related from VICIfast
- The VICIdial reporting suiteOutbound, inbound and agent reports, run live, with exports and scheduled email.
- A white-label webphone in your brandA WebRTC phone inside the agent screen on every server, in your colours.
- Dedicated hosting pricesAMD EPYC dedicated cores for steady volume or visible CPU steal.
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. “Why VICIdial dispositions take seconds to save”. VICIfast LLC, November 21, 2026. Retrieved from https://vicifast.com/blog/why-vicidial-dispositions-save-slowly
Have questions?
Related posts

Guides & tutorials
Reports and tools that slow a live VICIdial floor

Guides & tutorials
MyISAM table locks in VICIdial, explained without the database jargon

Guides & tutorials
Where agents connect in a VICIdial cluster: screen from one machine, phone from another

Guides & tutorials
Mapping your old dispositions to VICIdial statuses
You might be interested in
Guides & tutorials
When a CRM polls VICIdial once per agent: the load you don't see
Guides & tutorials
Idle campaigns left active: the hidden database load in VICIdial
Guides & tutorials
Why searching a lead by phone number freezes VICIdial, and the missing index

Guides & tutorials
Keep the call log small: log archiving on a busy VICIdial database
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.