Specified key was too long;

Did this happen with the latest (1.3.3) version of the plugin? If you used an earlier version please upgrade. That version upgrades your tables to use the InnoDB storage engine and the DYNAMIC row format.

If you did use v1.3.3, there’s a bug somewhere in my plugin. To help me figure it out, please visit the About tab on your Tools / Index MySQL page, upload your metadata, and let me know the upload key.

Thanks for your patience with this!

Hi there,

Yes, with a new 1.3.3 version.

The upload key is: 89vMUy9rzk

Also, note it is a staging site. If you want to try it on the staging site, I can give access to it.

Best,

I see you’re using MariaDB 10.1.48. I haven’t (yet) tested the plugin on that version. (It is no longer supported.)

I didn’t yet test the plugin on that version. I suspect it uses an older version of the InnoDB storage engine that doesn’t support covering indexes.

I’ll test with it (if I can figure out how to install it), and issue an update to the plugin if possible.

Sorry for the inconvenience.

Yeah, we have that from default Cloudways hosting settings… If you want, they have 3 days free trial anyway where you could test it.

I can try to upgrade to MariaDB 10.4 during the weekend, maybe that fixed it.

Thanks.

Yes, upgrading to MariaDB 10.3 or 10.4 will fix this problem. And, it should provide other performance and integrity enhancements: The MariaDB team has been hard at work since 2014 when 10.1 was released.

I have a fix, to support older versions of MariaDB, in the plugin too. You can try this plugin version (not yet released to the plugin repo) by downloading and installing this zip file.

https://www.plumislandmedia.net/static/index-wp-mysql-for-speed.zip

• This reply was modified 3 years, 5 months ago by OllieJones.

Yeah, today morning we did an upgrade to MariaDB 10.4, and indeed it fixed it. Didn’t have time to reply here, but it’s working now.

However, I’m not sure if you could assist us, but we tested PHP upgrading to 8.0 and database to MariaDB 10.4 for our staging site, which resulted in 5-6 seconds of product saving (it included setting up your plugin)

We now did the same for our live website, but product saving still takes something like 12-25 seconds, sometimes even longer…

Any advice here?

Try using the latest version of my plugin to monitor your database operations while you run the product saving operation. It will identify the queries taking the most time.

Thanks for that.

Issue solved – Wp rocket preload was causing it.

Now, 4-6 second load time while saving products.

Will install your plugin for another 3 websites.

Appreciate your hard work!

Best,

Thanks for the followup, and I’m happy to hear you solved your problem. I reached out to WP Rocket asking whether they have any compatibility issues I should know about.