enghell

Hello, I’ve solved this issue.

Some details: this is not a multisite, but rather a wildcard domain site, our audit logs table had about 2gb of data, and what was happening is the code to update the engine of that table was timing out, due to execution limits, but the query in MySQL ran, but since the code didn’t fully execute the version stored in the options table was never updated.

This led to almost each request to the site sending the alter table statement, locking that table for seconds, and then that table lock piled up on each new request.

I had to do some DevOps to fix it, but my first recommendation is to a) check if the engine is already changed for the task, in case the code is terminated due to time execution limits, or other reasons, most of the time the DB will still execute the query.

b) add a wp-cli command to execute these kind of tasks, and do not run them on plugin activation specially if they are possible heavy DB modifications, prompt the user to press a button in the backend to run them (see examples, WooCommerce)

In any case thanks for your reply.

Hello, thank you for replying to my feedback, I’m looking forward for that update.

Again thanks, your reply has helped me notice, the compatibility settings related to wp-stateless and imagify come from wp-stateles and not your plugin, thanks for the support.

Any input on this?