vicidial.org

Hello. When I click on the campaign setup on the system, it takes about 5 or more seconds before it populates and 10 seconds on clicking DETAILS. It has lists of 330K dialables leads combined. Thank you.

ViciBox v.9.0.2 200415-1712
VERSION: 2.14-757a
BUILD: 200619-1643
Asterisk 13.29.2-vici
1 Data/Web-6 cores 16gb
3 Telephony-6 cores 8gb
Cloud
SSD

Anybody encountered this before and could share about what they've done to resolve it? Thank you.

How many total leads?

Please post your database hardware specs, including drives and RAID.

Cloud

um ... you mean "virtual server instace" hosted at Amazon? Be specific ... it matters.

Hi Matt, it has 320K total leads.
320 GB SSD, 6 CPU, 16GB RAM.

@William, yes, its virtual server instance hosted at Vultr.

Thank you.

Are my resources not adequate? Thanks.

they are, however virtual servers are less stable and have been known to come across issues. I found that out the hard way lol

Thanks. Did this occur to you also before? Where only by clicking CAMPAIGN that it takes longer for just 320k leads? If so, what steps did you take to resolve it.

Regards.

Yes the more leads the slower it loads especially in virtual. Try putting some inactive if they're separate lists...

carpenox wrote:Yes the more leads the slower it loads especially in virtual. Try putting some inactive if they're separate lists...

changing to inactive has no effect. that changes a "Y" to an "N" in the "vicidial_lists" table without altering the size of "vicidial_list" (Note the missing "s"). Which means any query running on the vicidial_list table will not even notice the difference, as a rule. If you verify the time of the mysql response, there isn't likely to be a difference until you delete leads (or move them to an archived leads table) and optimize vicidial_list.

thanks Bill, i didnt realize that, i was figuring with them inactive it would try to pull any information on them from the db

carpenox wrote:thanks Bill, i didnt realize that, i was figuring with them inactive it would try to pull any information on them from the db

That's why I mentioned it. It's an easy assumption to make, and to test. Note that you are partially right: It does not try to get that information from the DB. But it has to sort through that information to get what it does need. Finding my mom at the train station is a lot easier when she's the only one there. When the place is packed nut-to-butt with peeople it's nearly impossible. It's not about what you're looking for, it's about the data set being searched. Wait! I got another one: Find the needle on the sewing table vs the haystack? lol

LMAO @ nut-to-butt

good shit