GMT Cron creating issue on calling

All installation and configuration problems and questions

Moderators: gerski, enjay, williamconley, Op3r, Staydog, gardo, mflorell, MJCoate, mcargile, Kumba, Michael_N

GMT Cron creating issue on calling

Postby pratikvicidial » Sun Mar 12, 2023 4:46 am

We have vicibox 9 installed with cluster 1db + 6 web & dailer servers.

Here we are facing issue with GMT cron it takes too much of times in some case execute again in next interval set taking mysql at high load. Which is impacting the calling functionality.


Currently we are having calling on same timezone and total lead counts are 11870842.

So what is best way to optimize the issue.
pratikvicidial
 
Posts: 29
Joined: Tue Mar 30, 2021 5:56 am

Re: GMT Cron creating issue on calling

Postby mflorell » Sun Mar 12, 2023 7:32 am

What is your hardware configuration for your database server?

Do you actively dial on all 11 million of those leads every day?
mflorell
Site Admin
 
Posts: 18335
Joined: Wed Jun 07, 2006 2:45 pm
Location: Florida

Re: GMT Cron creating issue on calling

Postby pratikvicidial » Sun Mar 12, 2023 7:54 am

AMD Epyc 7313 - 16c/32t - 3GHz/3.7GHz
64 GB RAM
4× 960GB SSD SATA Hard RAID

Currently we have 200k leads activate and calling is about for 100k.

Thanks
pratikvicidial
 
Posts: 29
Joined: Tue Mar 30, 2021 5:56 am

Re: GMT Cron creating issue on calling

Postby mflorell » Sun Mar 12, 2023 8:51 am

I would strongly encourage you to archive or delete the leads that you will not be dialing anymore if possible. On a high-end database server, performance falls greatly after you get past 10 million active leads, so it is best to delete or archive leads once you get past that point. On lower-end database servers, that magic number is 2 million active leads.

Archiving leads means you cannot dial from them anymore, but they are still accessible to search for within the admin web screens.


Here is an example of how to archive leads in MySQL:

CREATE TABLE vicidial_list_archive LIKE vicidial_list;
ALTER TABLE vicidial_list_archive MODIFY lead_id INT(9) UNSIGNED NOT NULL;

select count(*) from vicidial_list where list_id IN('9998','100','110','120','150','170','180','200','250','300','350','400','450','500','550','600','650','700','800','850','900');

INSERT INTO vicidial_list_archive SELECT * from vicidial_list where list_id IN('9998','100','110','120','150','170','180','200','250','300','350','400','450','500','550','600','650','700','800','850','900');

select count(*) from vicidial_list_archive where list_id IN('9998','100','110','120','150','170','180','200','250','300','350','400','450','500','550','600','650','700','800','850','900');

DELETE from vicidial_list where list_id IN('9998','100','110','120','150','170','180','200','250','300','350','400','450','500','550','600','650','700','800','850','900');

optimize table vicidial_list;
mflorell
Site Admin
 
Posts: 18335
Joined: Wed Jun 07, 2006 2:45 pm
Location: Florida

Re: GMT Cron creating issue on calling

Postby covarrubiasgg » Wed Mar 15, 2023 11:15 am

I always change that cron to be run 2 hours before operation start because at some point it always causes me issues. If agents starts dialing at 7:00 a.m. I perform a reboot at 4:30 and run the GMT update at 5:00
covarrubiasgg
 
Posts: 420
Joined: Thu Jun 10, 2010 10:20 am
Location: Tijuana, Mexico


Return to Support

Who is online

Users browsing this forum: Google [Bot] and 83 guests