Disk space issues are common, and they’re often difficult to
solve quickly. One way to recover some space is by enabling
InnoDB compression.
First, of course, you want to make sure you’ve covered
alternative solutions. Can you archive data? Do
partitioning/sharding? These generally involve application
changes and can take longer.
You may need to first do conversion to InnoDB.
While compression is available for MyISAM via myisampack, and
this can be useful for some use cases (for example, if you are
rotating out tables on a monthly basis), it makes the tables
read-only, so generally you will want to first convert MyISAM
tables to InnoDB.
Things to watch for in the schema: After working on functional
and performance issues with full-text indexes after conversion to
InnoDB, I wouldn’t recommend it. Application changes are also
required to rewrite queries. You can consider outsourcing these
to a tool …
[Read more]