Automatic Trim Hopper

[jessiekidfernando]

Hello Everyone,

What is the downside if the Auto Trim Hopper is not set to Y?

Minimum Hopper Level:5000
Automatic Hopper Level:Y
Automatic Hopper Multiplier:4.0
Auto Trim Hopper:N
Hopper VLC Dup Check:Y
Manual Dial Hopper Check:N
Force Reset of Hopper:N
Dial Method:ADAPT_TAPERED
Auto Dial Level:30
Auto Dial Level Threshold:DISABLED
Available Only Tally:Y
Available Only Tally Threshold:NON-PAUSED_AGENTS
Drop Percentage Limit:5%
Maximum Adapt Dial Level:30
Latest Server Time: 1900
Adapt Intensity Modifier:-7 -Less Instense
Dial Level Difference Target: -7 --- 7 Agents Waiting for Calls
Dial Level Difference Target Method: ADAPT_CALC_ONLY

[mflorell]

If your other hopper settings are set properly for the campaign you are on, nothing.

We've had issues with clients that had wide variations in the number of agents that are in a campaign throughout the day and that is why that feature was created in the first place.

[williamconley]

I'm gonna toss a "guess" into this thread.

You've found that loading the hopper takes a long time. So you've dramatically increased the size of your hopper to reduce the number of times it slows the system down. Now your hopper is at 5k and it still hammers the system, but not as often.

IF this is true: you're doing it backwards. Reducing the hopper to the number of leads you will dial in one minute, in an otherwise properly configured system, allows a small hit every minute that doesn't hammer the system. Set the hopper level to 50 (or 5) and set it to automatic. Watch the hopper level, and if it never even considers hitting "zero" before it reloads, consider changing the hopper multiplier to a lower number. The less leads in the hopper, the less leads it "searches for" every minute. If you can get that down low enough there is NO sysem disruption during that search to load the hopper. Back in the earlier days of robodialing, this was a constant battle until these methods were adopted.

Of course, there are other causes for slowness during hopper load. For instance: more than 5M leads in the vicidial_list table can be problematic (archive or delete those not needed right now). Lots of reports being run (replication server!). But continuing to increase the hopper level can be problematic over time.

The Hopper DOES have a maximum level. It's a memory table. MyISAM memory tables have limits. Also worthy of note: The reason the hopper table exists is to reduce mysql load during "dial the next number". The goal is to have a small list from which the dialer will grab "the next lead" to dial instead of having to search the entire Vicidial List table. Growing the hopper table to huge levels defeats this purpose and loads up the mysql server having the opposite effect of that goal. Thus if you have campaigns not in use that have huge hoppers, deactivate them and clear their hoppers.