From 5.5, the INNODB engine can also be compressed like the MYISAM engine. Of course, the compressed table is okay. You should not INSERT or UPDATE it. DELETE doesn't matter. It's just MARK, and then batch DELETE it. This
From 5.5, the INNODB engine can also be compressed like the MYISAM engine. Of course, the compressed table is okay. You should not INSERT or UPDATE it. DELETE doesn't matter. It's just MARK, and then batch DELETE it. This
From 5.5, the INNODB engine can also be compressed like the MYISAM engine. Of course, the compressed table is okay. You should not INSERT or UPDATE it. DELETE doesn't matter. It's just MARK, and then batch DELETE it. This is the same as the BRIGHTHOUSE engine.
Of course, not all tables are suitable for compression, website space, and then reading. Application scenarios, data distribution, virtual hosts, and hardware resources all restrict compression. At this time, the best way for a VM is to perform a stress test to see if it is suitable for your own business.
The following are some new features of the compressed table.
1. the compressed table is only valid for a single tablespace. Therefore, set the following parameters:
Innodb_file_per_table
Innodb_file_format = Barracuda
2. Create Table OPTIONS.
ROW_DATEFORMAT = COMPRESSED
KEY_BLOCK_SIZE = (1, 2, 4, 8, 16 .)
The proper size of KEY_BLOCK_SIZE depends on the data distribution of the table to be compressed. Simply put, you can use the same data to insert tables of different structures. After you finish viewing the size of the disk table, you will be OK.
3. Pay attention to another feature.
If INNODB's compressed table is set, your INNODB_BUFFER_POOL_SIZE should be at least twice the previous size. Because two pages with different sizes but consistent data must be retained in the buffer pool. In this way, the memory overhead is increased.
This article is from "god, let's see it !" Blog, please keep this source