Last post by Arantor -
I wanted to like the last post (because it's about time we stopped encouraging 'optimize table' as a thing that people should 'just do') - but I couldn't like any post in this topic. Not sure if that's by intent (since there were likes in this topic before, but I can't like anything here now. Other topics seem to be fine.)
Last post by Spuds -
If you are running InnoDB as your storage engine, then it will not "optimize" those tables.
Doing optimize on an InnoDB table is usually not necessary (unlike MyISAM). Maybe after you have done A LOT of insert/update/delete against the table IN A WAY that could result in fragmentation. Perhaps if you are using a FULLTEXT search index on an InnoDB table, that may benefit from DROP INDEX, then ADD INDEX but optimize really does a ALTER TABLE ... FORCE on InnoDB whichi is mostly a don't bother with our tables.
You are much better off tinkering with your conf file if you want to optimize InnoDB.
I recall some discussion on what the real IP is when using cloudflare or some others, Its in one of the x-headers. Do a site search on cloudflare and see if those solutions will work for you. But like @tino said, that IP should not change in session.
Last post by optimizerdude -
Did something change with the optimizing database function? Before it worked flawlessly, and now no matter what, it says there is nothing to optimize even though major changes were made to database.
Also can we fix the token verification failed error? I think it has to do with the user coming from different IP's if the hosting is behind a DDOS protection service like cloudflare.