compression
A feature with wide-ranging benefits from using less disk space, performing less I/O, and using less cache memory. InnoDB products include more than one feature related to compression: table data can be kept in a compressed format during database operation; data can be compressed as part of a backup operation with the MySQL Enterprise Backup product.
When InnoDB table data is compressed, the compression applies to the table itself, any associated index data, and the pages loaded into the buffer pool. Compression does not apply to pages in the undo buffer.
The table compression feature requires using MariaDB 5.5 or higher, or the InnoDB Plugin in MariaDB 5.1 or earlier, and creating the table using the Barracuda file format and compressed row format, with the innodb-file-per-table setting turned on.
The compression feature of the MySQL Enterprise Backup product makes a compressed copy of each tablespace, changing the extension from .ibd to .ibz. Compressing the backup data allows you to keep more backups on hand, and reduces the time to transfer backups to a different server. The data is uncompressed during the restore operation. When a compressed backup operation processes a table that is already compressed, it skips the compression step for that table, because compressing again would result in little or no space savings.
See also Barracuda.
See also buffer pool.
See also compressed row format.
See also hot backup.
See also index.
See also innodb-file-per-table.
See also plugin.
See also table.
See also undo buffer.