The Pool properties can be set with: ceph osd pool set compression_algorithm Ĭeph osd pool set compression_required_ratio Ĭeph osd pool set compression_min_blob_size Ĭeph osd pool set compression_max_blob_size Bluestore Compression Internalsīluestore won’t compress any write that is equal or less than the configured min_alloc_size. The compression_mode, compression_algorithm, compression_required_ratio, compression_min-blob_size, and compresion_max_blob_size parameters can be set either via a per-pool property or a global config option. Uses compression under all circumstances even if the clients hint that the data is not compressible. Passive: Do not compress data unless the write operation has a compressible hint set.Īggressive: Compress data unless the write operation has an incompressible hint set.įorce: Try to compress data no matter what.
The different compression modes provided by BlueStore are: Whether data in BlueStore is compressed is determined by a combination of the compression mode and any hints associated with a write operation. In this blog we will take a deep dive into BlueStore’s compression mechanism and understand its impact on performance. In addition to this, using the Ceph CLI the compression algorithm and mode can be changed anytime, regardless of whether the pool contains data or not.
Compression can be enabled or disabled on each Ceph pool created on BlueStore OSDs. With the BlueStore OSD backend, Red Hat Ceph Storage gained a new capability known as “on-the-fly data compression” that helps save disk space.
0 kommentar(er)
