Is MySQL optimize table request safe to use during write operations and in replication enviorement?

Clash Royale CLAN TAG#URR8PPPIs MySQL optimize table request safe to use during write operations and in replication enviorement?
I have MySQL DB with up to 300 InnoDB tables with similar structure each has about 700k rows and size around 160M in normal case. This tables are independent of each other and has no foreign keys.
This tables are intensively used for RW operations the table usage pattern looks like this:
After a few month the DB performance has dropped significantly. After investigation the problem was found: the table files has grown large and occupied about 300M of disk space each. After running manual table optimization the problem was solved but in a few weeks the DB performance started to degrade again.
As a solution to keep DB healthy the OPTIMIZE TABLE request was added after each data removal.
The questions are:
By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.