MySQL InnoDB Engine Table Compression, which reduces the size of database size, reduces the CPU I/O and improve overall throughput time.

The compressed data requires the small size of pages, compare to uncompressed data.
MySQL implements compression with the help of the well-known zlib library, which implements the LZ77 compression algorithm.

This compression algorithm is mature, robust, and efficient in both CPU utilization and in a reduction of data size.

Because of compressed data, processors and cache memories increases the speed of execution.
Internally buffer pool fetches the compressed data, uncompressed that data, perform the operation and again write compressed data into Disk.

The default uncompressed size of InnoDB data pages is 16KB.

If innodb_file_per_table variable enable, only we can create compressed table.

For InnoDB system tablespace, we cannot create compressed table because the single InnoDB ibdata1 file also contains other metadata information which we cannot compress.

You can access below articles for more details on InnoDB data files.

MySQL: Why InnoDB Engine stores all databases in one file (ibdata1)?

MySQL: The Truth about InnoDB File Per Table Tablespaces

Mostly, we should enable compression for a read-intensive type of application where RAM frequently uses data.
The default uncompressed size of InnoDB data pages is 16KB and Depending on the combination of option values, MySQL uses a page size of 1KB, 2KB, 4KB, 8KB, or 16KB for the tablespace data file (.ibd file).

How to create an InnoDB Compressed Table?
First In my.cnf or my.ini, innodb_file_per_table required to enable and innodb_file_format must be set to Barracuda.

SET GLOBAL innodb_file_per_table=1;
SET GLOBAL innodb_file_format=Barracuda;

We can create a table with an ROW_FORMAT=COMPRESSED option, which set compressed value half of the innodb_page_size variable.
Explicitly, we can also set a KEY_BLOCK_SIZE value to give a hint.
Here, You can check the size of innodb_page_size. (default 16KB)

SHOW VARIABLES LIKE 'innodb_page_size';

Create Sample InnoDB Compress Table (Set to 8KB):

CREATE TABLE tbl_CompressedTable
(
	CID INT PRIMARY KEY
	,CName VARCHAR(50)
)
ROW_FORMAT=COMPRESSED
KEY_BLOCK_SIZE=8;

In this post, I am going to discuss MySQL InnoDB File-Per-Table tablespaces.
What are the advantages and disadvantages? How to enable and disable it?

By default, The InnoDB stores tables and indexes into the system tablespace. If we want to create separate .idb and .frm file for each table, we should enable innodb_file_per_table.

How to Enable and Disable Innodb_file_per_table?

To Enable:
Add below line into [mysqld] section of my.cnf file and restart the MySQL Server. It will create two separate file for each table, .idb file for data and .frm file for table definition.

[mysqld]
innodb_file_per_table=1

-- We can also run this command and restart MySQL Server. 
SET GLOBAL innodb_file_per_table=1;

To Disable:
Simply, you can remove innodb_file_per_table line from my.cnf and restart the server. Now newly created table stores into common tablespace (ibdata1).

Advantages to enable innodb_file_per_table:

• The Truncate Table operation runs faster when we have separate.idb file.
• We can reclaim disk space by truncating and dropping a single table. On the other side, with the single table space we can use this free space only for new InnoDB data.
• We can easily run OPTIMIZE TABLE on individual Table files.
• We can easily store and move individual table.
• We can use features like compressed and dynamic row formats.
• We can quickly perform backup and restore of individual tables.

Disadvantages to enable innodb_file_per_table:

• The management of each different file is very difficult and time taking exercise.
• Each different file has unused space so we require to perform OPTIMIZE TABLE on each individual file.
• Mysqld has to open file handler per table, which may reduce the performance of MySQL Server.
• For every action of each file buffer pool is scanned, which reduce the performance of MySQL Server.