muyousif wrote:Thanks Proper for your detailed reply actually Database is daily checked and repaired nightly, all servers are restarted early in the morning. I am continually monitoring server loads and looks quite fine. One Database server with three telephony server with almost 100 agents and dialing ratio is 2. I am also part of carrier so at the same time I see carrier server and vicidial, Calls connected at "carrier server" are always 10 to 15 calls more than the calls "connected" shown by vicidial (agent in calls + calls waiting for agents). There are two more issues reported by the agents with this issue
1. Sometimes called number is not shown on the agent page when agent is in live call.
2. Caller or lead information in live call is shown after "10 to 20" seconds being in call.
Any idea?
Delays like that almost always indicate high load on DB server. Delays in pulling information are just visible issues, but there are likely bigger issues going on under the hood, if database is overloaded.
Do you run archive process for your log tables?
What is the record count or size, of your database and specifically log tables?
Is your web server on same server as DB?
Large volume deployments need considerations with database architecture-
1) Controlling size of your database key tables.
2) Properly configuring database itself for types of queries that are most demanding in vicidial
3) Making sure server configurations like "open file limits" do not inhibit DB performance.
4) Getting appropriate hardware for Mysql deployment, and scaling with replication systems if necessary
Fist thing to check is ram consumption on DB server. It could be just running out and "swapping".
If database is just large - millions of records in log tables, or millions of records in leads - then you need to work on a plan to maintain that. Logs need to be archived, leads can be shifted of managed otherwise.
Let me know what you discover.