Optimizing InnoDB tables

Following the thread. I would love more information on this as well.

Thank you,
Robert

It looks as though the latest update created more problems than it solved. Optimize worked fine to my knowledge before the update and now the main use for it is no longer available. I used the plugin to optimize the database. Now I can not optimize the database at all without checking the option to also optimize the innodatabase – which we are informed comes at a unknown risk.

So can anyone please provide clarity on the matter: If we want to optimize the database we must also agree to optimize the innodatabase. Why is an all or nothing new “selection?” It was not this way prior to the update.Also if we do update with the innodatabase (which is the only recourse now) what are the risks?

What other plugin could we use while this is being resolved?

Also, can we uninstall the updated new version and simply use the previous version before the latest update?

That previous version worked fine. The newer version blocks the ability to simply optimize your database without requiring the innodatabase option that is supposed to be more risky.

Watching this thread as I too wonder why even have this plugin if it can no longer optimize my database?

It is odd. If you click on the option to optimize your tables and database (which I get are one in the same, you can’t use that option unless you also click on the optimize Innotables (whatever they may be). Yet we’re cautioned not to use that feature unless we know what (I guess) it could do by happenstance?

Of course if I were expert in optimizing database tables, I wouldn’t need the plugin. So, I think it’s fair to say the last update kind of removed the point to having it for many of us out there.

Can anyone recommend a new plugin that would enable the now-missing feature as long as it won’t jack up one’s website database?

Hi,

Apologies, it appears that the correct FAQ is missing from the linked FAQ page.
We have just launched a new site, and the FAQ link was missed in the update.
The correct FAQ is here:
https://getwpo.com/faqs/why-we-dont-optimize-innodb-tables/

The reason for the warning is that optimizing InnoDB tables in MySQL 5.6 or earlier is ineffective and inefficient, as it essentially rebuilds the entire table. However, on newer versions of MySQL (and MariaDB), this issue is resolved.

If the option to optimise database tables is disabled unless the InnoDB override is enabled, this suggests that there are no non-InnoDB tables in the database. A count of InnoDB tables and other tables should be displayed in the option notes.

If your MySQL version (shown in the Status box) is 5.7 or higher, then the warning can be ignored.

DNutbourne

Thank you for the explanation, however that is not how it is working on my install.
You said: If the option to optimise database tables is disabled unless the InnoDB override is enabled, this suggests that there are no non-InnoDB tables in the database. A count of InnoDB tables and other tables should be displayed in the option notes.:

But WP-Optimize tells me:

“Tables using the InnoDB engine (11) will not be optimized. Other tables will be optimized (20).”

Yet I cannot choose to optimize with also selecting “Optimize InnoDB tables anyway.”

Not that I have a ton of other tables, but still, not functioning as you explained.

I ditto mrkingid’s response above. For me, it’s “Tables using the InnoDB engine (3) will not be optimized. Other tables will be optimized (45).” I cannot do anything unless I tick the “Optimize InnDB tables anyway” button.

I’m having the same problem. My InnoDB talbes are 32 and the oters MyISAM are 46, but I can’t optimize them enymore because MySQL is 5.6.36 version. Am I right? Is there a possible solution?
Thank you

Can anyone out there tell me – with the latest version of WP Optimize – whether it is safe to optimize InnoDB tables, or not safe? Simple question, perhaps hard to answer.

Hi,

This has been re-worked in the just-released 2.2.1 release. Please update, and if you still have trouble, open a new topic.

@robvanhummel2015 – it depends. In modern MySQL/MariaDB releases, there can be lots of different permutations of how InnoDB works. We believe that the latest release now reflects this more accurately and flexibly. Please give it a try!

David

I am able to optimize again with the update. Thank you for your quick response to this David!

David @davidanderson, just so we can understand a little bit better with the InnoDB question. Is it unsafe or unwise to select the “optimize InnoDB” option or only wise under certain circumstances? When I click on the link to read about the potential dangers of optimizing a InnoDB, it takes me to a FAQ page where the specifics are still vague. Is it that optimizing the innodb is not necessary or that it simply doesn’t do very much to impact the speedy loading of a site? Or are there other reasons not to use it unless certain factors are at play? Can you please elaborate just so we’re more informed on the “optimize Innodb” feature. Should we use it only under set circumstances or conditions? Are there times when it’s not advisable? It’s still not clear and I’d like to better understand what is safe and not safe.

Thanks.

Thank you David @davidanderson! This is exactly my point. I just want to know whether or not it is safe to select “optimize InnoDB anyway”. Cab someone at WP Optimize please answer this question. I don’t want to mess up my website(s), so therefore I need to know whether it it is safe and useful to optimize InnoDB “anyway”. Even the FAQ is not clear about this.

Thanks!

Yes. Thank you DavidS, and robvan…, and the others. Let’s get a comprehensive, clear explanation of when and why and what. We’re coming closer. I’m parked here to stay on top of it.

Thank you!