If you enable compression for fields, attributes, and indexes, the storage space occupied by these objects is reduced. However, the query performance is adversely affected. We recommend that you evaluate the impact before you enable data compression.
Suggestions:
We recommend that you do not enable compression for indexes, fields, or attributes that are frequently accessed.
We recommend that you do not enable compression for hot spot fields.
After data compression is enabled, the query performance is adversely affected. We recommend that you test the impact of data compression on query performance in a test cluster. For example, you can check the metrics such as the query response time and cluster load after data compression is enabled. If the impact on your business is acceptable, you can modify your online cluster to enable data compression.
Optimization method after data compression is enabled:
After data compression is enabled, the query performance is adversely affected. However, you can use an index table loading policy to offset some of the impacts. For more information, see Configure an index table loading policy. The following section describes the configuration method:
In the cache policy, add the following parameter to the load_strategy_param section in load_config:
"cache_decompress_file": trueThis parameter is used to enable caching for compressed data. You can set this parameter to true if you enable data compression. This reduces the impact of data compression on performance.