Hooper loads slow when we use list mix

[rameez.amjad4]

Good Day,
I am having this issue need your assistance,

We are using list mix option for dialing, selected 2 lead sets in a campaign each lead set having 400k records,

When we use list mix and hooper level is set to 5000 with automatic hooper multiplier set active to 4.0, when hooper gets empty and tries to load leads from list mix it takes around 5 seconds to get leads in hooper from list mix and in mean time calls those are already placed by dialer drops in those 5 seconds and when hooper is loaded again it sends calls to agents so our mostly calls are dropped.

We are using list mix, dial method is ADAPT_TAPERED.

But when we use a single list instead of list mix it works fine as compare to list mix?

[mflorell]

One of the many reasons we recommend that people don't use list mix.

Although, it could be an issue of underpowered database hardware. What are the specs on your database server? (hard drives, CPU, Memory, RAID card, etc...)

[williamconley]

Good Day,
I am having this issue need your assistance,

We are using list mix option for dialing, selected 2 lead sets in a campaign each lead set having 400k records,

When we use list mix and hooper level is set to 5000 with automatic hooper multiplier set active to 4.0, when hooper gets empty and tries to load leads from list mix it takes around 5 seconds to get leads in hooper from list mix and in mean time calls those are already placed by dialer drops in those 5 seconds and when hooper is loaded again it sends calls to agents so our mostly calls are dropped.

We are using list mix, dial method is ADAPT_TAPERED.

But when we use a single list instead of list mix it works fine as compare to list mix?

1) Welcome to the Party!

2) As you are obviously new here, I have some suggestions to help us all help you:

When you post, please post your entire configuration including (but not limited to) your installation method (7.X.X?) and vicidial version with build (VERSION: 2.X-XXXx ... BUILD: #####-####).

This IS a requirement for posting along with reading the stickies (at the top of each forum) and the manager's manual (available on EFLO.net, both free and paid versions)

You should also post: Asterisk version, telephony hardware (model number is helpful here), cluster information if you have one, and whether any other software is installed in the box. If your installation method is "manual/from scratch" you must post your operating system with version (and the .iso version from which you installed your original operating system) plus a link to the installation instructions you used. If your installation is "Hosted" list the site name of the host.

If this is a "Cloud" or "Virtual" server, please note the technology involved along with the version of that techology (ie: VMware Server Version 2.0.2). If it is not, merely stating the Motherboard model # and CPU would be helpful.

Similar to This:

Vicibox X.X from .iso | Vicidial X.X.X-XXX Build XXXXXX-XXXX | Asterisk X.X.X | Single Server | No Digium/Sangoma Hardware | No Extra Software After Installation | Intel DG35EC | Core2Quad Q6600

3) Let me get this clear:

Your hopper level is set to 5000 with multiplier of 4.0 on ONE campaign, and you actively run out of leads in the hopper? So you dial 20,000 leads in one minute? This would be a fairly major installation with multiple servers. But you didn't list hardware specs or any version information at all (which is fairly normal for a newbie, but not so much for a major user). So I'm a little confused as to whether you are really dialing that heavy, or if you noticed that loading leads into the hopper took a while once, then decided to just load MORE leads into the hopper to solve the problem, and kept doubling down on that until you ended up where you are today.

IF that's the case, then your solution is to load ONLY the number of leads you require per minute and find out what other query is slowing down your vicidial_list table causing leads to load slowly sometimes. Any complex query involving the vicidial_list table, or even a simple query without a proper index, can slow down hopper loading and cause the reflex to try to "put more in the hopper", which is counterproductive in the end as loading 20000 leads into the hopper then has major impact on the vicidial_list table and will fight with whatever other query you have slowing down the system for control. Snowball effect, and the system never catches up.

[rameez.amjad4]

One of the many reasons we recommend that people don't use list mix.

Although, it could be an issue of underpowered database hardware. What are the specs on your database server? (hard drives, CPU, Memory, RAID card, etc...)

We are using Dell Power Edge T620 , with dual octa core prcessors, 32 gb Ram, and 500 GB Hard Drive on Raid 0, i installed server yesterday Vicibox 8.1.2 (Vicibox-express), but same issue, please update why we get this issue when we use vicidial but on other side when we use goautodial 3.3 64 bit it works weel with that, Please update and suggest how can i make this work, Thanks.

[rameez.amjad4]

Please reply back, Thanks.