For example: SET GLOBAL innodb_compression_algorithm = 'lzma' This system variable can be changed dynamically with SET GLOBAL. From MariaDB 10.7, algorithms can be installed as a plugin. However, on many distributions, the standard MariaDB builds do not support all InnoDB page compression algorithms by default. Pages are compressed using the snappy algorithm. Pages are compressed using the bzip2 compression algorithm. Pages are compressed using the lzma compression algorithm. Pages are compressed using the lzo compression algorithm. Pages are compressed using the lz4 compression algorithm. This is the default value in MariaDB 10.2.4 and later, and MariaDB 10.1.22 and later. Pages are compressed using the bundled zlib compression algorithm. This is the default value in MariaDB 10.2.3 and before, and MariaDB 10.1.21 and before. This system variable can be set to one of the following values: This means that InnoDB supports having uncompressed pages and pages compressed with different InnoDB page compression algorithms in the same InnoDB tablespace at the same time. InnoDB is able to handle this situation without issues, because every page in an InnoDB tablespace contains metadata about the InnoDB page compression algorithm in the page header. When this system variable is changed, the InnoDB page compression algorithm does not change for existing pages that were already compressed with a different InnoDB page compression algorithm. Innodb_compression_algorithm system variable. However, the server-wide InnoDB page compression algorithm can be configured by setting the There is not currently a table option to set different InnoDB page compression algorithms for individual tables. See Storage Engine-Independent Column Compression - Comparison with InnoDB Page Compression.Ĭonfiguring the InnoDB Page Compression Algorithm.Comparison with Storage Engine-Independent Column Compression In general, InnoDB page compression is superior to the COMPRESSED row format. This means that the COMPRESSED row format has less compression options than InnoDB page compression does. In contrast, with InnoDB's COMPRESSED row format, zlib is the only supported compression algorithm. With InnoDB page compression, multiple compression algorithms are supported. This means that the COMPRESSED row format re-compresses data more frequently than InnoDB page compression does. These changes are then occasionally flushed to disk. In contrast, with InnoDB's COMPRESSED row format, pages are re-compressed immediately after any changes, and the compressed pages are stored in the buffer pool alongside the uncompressed pages. With InnoDB page compression, pages are compressed just before being written to the tablespace file.This means that the COMPRESSED row format uses more space in the buffer pool than InnoDB page compression does. In contrast, with InnoDB's COMPRESSED row format, compressed pages are decompressed immediately after they are read from the tablespace file, and both the uncompressed and compressed pages are stored in the buffer pool.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |