can vicidial_live_agents be a MEMORY table?

[bobbymc]

does that table require table locks?

[williamconley]

I would think it would be fine as a memory table. If you wanted to try it, I sincerely doubt it would break anything. Obviously a backup would be good before trying it. I don't expect it would ever get too large (100k live agents? unlikely, LOL).

[williamconley]

Oops. No text or blob fields in a memory table. bummer. of course, you could change closer_campaigns, agent_territories and external_ingroups to a (very long) varchar for this test.

http://dev.mysql.com/doc/refman/5.0/en/ ... ngine.html

The maximum size of MEMORY tables is limited by the max_heap_table_size system variable, which has a default value of 16MB. To have larger (or smaller) MEMORY tables, you must change the value of this variable. The value in effect for CREATE TABLE is the value used for the life of the table. (If you use ALTER TABLE or TRUNCATE TABLE, the value in effect at that time becomes the new maximum size for the table. A server restart also sets the maximum size of existing MEMORY tables to the global max_heap_table_size value.) You can set the size for individual tables as described later in this section.

[mflorell]

We've done it before and it eats up a ton of memory, since VARCHARs can't exist in MEMORY tables, they are converted to CHAR.

If you are operating with no inbound groups, or very few, then you can do it on a DB system with a lot of RAM if you reduce those fields to smaller CHAR fields.