We have a very large MySQL InnoDB database, compressed using the following syntax at the end of the table declaration:


We also have windows compression enabled on the logical disk drive that the database resides. It is an 800GB SSD hard drive. The drive is used solely for the database, no other files reside on it.

Does having the two compressions enabled help to save more space, or is it hurting or not beneficial at all?

  • If you have innodb_file_per_table then try copying some average one of the ibd files (preferably from a backup or let some admin do that for you) and try running it through rar/zip anything - I would be surprised it you get more than few percent and it will be quite slow - filesystem probably uses something fast so not as strong - but by doing small test you will see how "compressible" it is. In general once compressed data are close to "random" so another compression cannot do much. InnoDB cannot be as good as file compression tools as it needs to keep data organized a bit for fast access ... – jkavalik Aug 17 '15 at 6:03
  • ... so you will probably see at least some effect from your test run of zip/rar/other but if it is not in tens of percent range then I suggest it is not worth it as it slows down the access more than working with slightly bigger data. – jkavalik Aug 17 '15 at 6:05

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.