Events Manager – Database Structure

One other issue that popped-up in the last couple of days. Our site has been slowing down. When the Level 2 support of the hosting company looked at the site, they came back and said, in part, the slowness was due to the growing size of the WP database behind it. The database had grown to 500,000+ records; 300,000+ of which are in the postmeta table.

In looking through that table, we took out all post revisions, which removed very little content. As we continued to look through the table, we noticed that there was much record information with respect to plugins. (This was confirmed in the WordPress Codex as being normal.) Of those records, a majority of them were from EM. This makes sense, due to the number of recurring events we list in EM and many of those recurring events take place multiple times per week for a full year.

In communicating with WordPress, we suggested that in some future revision, maybe some thought could be placed into putting plugins (and themes) into their own database tables, instead of using the postmeta table.

I might suggest a similar for Events Manager. Would it be possible at some time in the future, to consider having Events Manager using its own table. I have to believe this would aid administration of a site and Events Manager, as well as allowing sites to run faster.

Just a thought…..