You should NOT repair tables that are not crashed, and you shouldn't optimize tables unless you've hard deleted lots of data from them. You could in theory destroy a table by repairing it when it doesn't need it.
Optimize does not function on any innodb tables unless the software is storing each unique innodb table as a file, which is uncommon.
If you're upset/annoyed at the "Overhead" displayed by innodb tables, I'd suggest getting over it. There is a tiny bug and we don't calculate overhead correctly for innodb, instead we show the entire innodb cluster files size. That means what you see as overhead is the total overhead for every single innodb table for an entire MySQL server, not your database.
|