The storage space used by different storage engines is relatively old)

The storage space is tight, and historical data is not changed. Originally, InnoDB uses the default compact format to store data;
To reduce space usage as much as possible, we compared several storage methods.
Rows = 14662062 in MySQL 5.1.48 with InnoDB plugin 1.0.9

Engine format Table Status OS file size
========================================================== ====================================
InnoDB-buildin compact 2319450112 + 3152019456 5557452800
MyISAM dynamic 2003505360 + 553457664 2003505360 + 553457664
InnoDB-plugin compressed (16 k) 2319450112 + 3148873728 5553258496
InnoDB-plugin compressed (8 K) 2321547264 + 3148873728 2789212160

ARCHIVE storage engine does not support btree, so we won't compare it here.
As you can see, using MyISAM or InnoDB-plugin compressed (8 K) to store data saves more than 50% of the space;
However, MyISAM does not adopt compression, so no additional CPU resources are occupied during reading;

After InnoDB-plugin compressed (8 K) compression, you still need to decompress it during reading, so more CPU will be consumed at that time;
In addition, whether the data is stored after being read to the bufferpool after being decompressed (16 K. I don't know yet; I 'd like to find a way to test it.