More importantly, I call BS on your hosting company. They know they suck, so they’re making shit up to appease you.

The optimize operation has very little to do with performance, especially on something like a WP blog. The main purpose of optimizing a table is actually to reclaim disk space (and even then it’s not necessarily a good idea). See here, including comments.

Moreover, the optimize operation automatically repairs a table before optimizing, as necessary, so there’s no need to repair and optimize separately.

As for repairs themselves, they should almost never be necessary. MySQL tables only get damaged if there’s something like a power outage or serious hardware failure during a database write. If that’s happening, your host really sucks.

Just about everything phpmyadmin does corresponds directly to a native MySQL command. You can learn to call your own BS by reading the docs here.

Of course, making all of that irrelevant — and the biggest reason of all to call BS — is that using wp-cache takes database operations out of the site load altogether for most page views.

All told, I praise your tech for his slick appeasement. Proposing a fake solution to a non-existent problem, in order to deflect attention from his employer’s shoddy service = genius. Well done, sir! I hope they’re paying you well.