Comments on: Pay Attention to Your WordPress Database

By: Kevin Muldoon

Kevin Muldoon — Mon, 13 Feb 2017 15:11:51 +0000

In reply to Patrick. It's crazy that the plugins that are being used to test plugins are causing major optimisation problems themselves. There should at least be some safeguards put in place to stop the database being filled up so quickly.

By: Patrick

Patrick — Mon, 13 Feb 2017 14:53:01 +0000

Had the exact same issue a few months ago. In fact, Performance Profiler caused so much strain on the server I was using it on, that it actually brought down a large client site for 10 minutes only a few hours after activating.

After looking into the DB, those same tables had grown to a collective 2 GB. So it really doesn’t take long for the plugin to do some major damage to your DB size.

You are right, though, in that it is ultimately the responsibility of the person installing rather than the developer. As you said, best to activate, use briefly and disable, and I would even stress that this is done only on a staging site and NEVER on a production site.

By: Kevin Muldoon

Kevin Muldoon — Mon, 13 Feb 2017 13:29:34 +0000

In reply to Patrick Steil.

Hi Patrick.

No the database is around 160MB now (I mentioned this in the post).

I recommend checking phpMyAdmin and then sorting by size to see which tables are causing the problem.

Kevin

By: Patrick Steil

Patrick Steil — Mon, 13 Feb 2017 13:22:21 +0000

Facing the same issue Kevin with a couple of other plugins. I would check the actual file size of your database file. I bet it is still at least 19.5gb. Would love to see a step by step on how to fix that problem.

Thanks!

By: Kevin Muldoon

Kevin Muldoon — Thu, 09 Feb 2017 22:23:00 +0000

In reply to kredi. Yes only one plugin caused this. A lot of plugins use too much space in your database.

By: kredi

kredi — Thu, 09 Feb 2017 22:15:00 +0000

Do this until the data has occurred due to only one add-ons?