Update tikv-configuration-file.md

pingcap · qiancai · Jan 25, 2024 · Jan 5, 2024 · Jan 5, 2024 · Jan 8, 2024
commit 3ca3d450f00f10e47ed6d35145da2319eb30b124
diff --git a/tikv-configuration-file.md b/tikv-configuration-file.md
@@ -1616,7 +1616,7 @@ Configuration items related to `rocksdb.defaultcf.titan`.
 
 ### `zstd-dict-size`
 
-+ The zstd compression dictionary size. The default value is `"0KB"`, which means Titan's compression is based on single values. But RocksDB compression is based on blocks (`32KB` by default). When the average size of Titan values is less than `32KB`, Titan's compression ratio is smaller than RocksdDB. Taking JSON as an example, Titan store size can be 30% to 50% bigger than RocksDB. The actual compression ratio depends on the value content and the similiarity among different values. You can set `zstd-dict-size` (for example, set it to `16KB`) to enable the zstd dictionary compression to increase the compression ratio. The actual store size can be lower than RocksDB. But the zstd dictionary compression can lead to about 10% throughput regression in a typical read-write workload.
++ The zstd compression dictionary size. The default value is `"0KB"`, which means to disable the zstd compression dictionary. In this case, Titan's compression is based on single values, but RocksDB compression is based on blocks (`32KB` by default). When the average size of Titan values is less than `32KB`, Titan's compression ratio is smaller than RocksdDB. Taking JSON as an example, Titan store size can be 30% to 50% bigger than RocksDB. The actual compression ratio depends on the value content and the similiarity among different values. You can set `zstd-dict-size` (for example, set it to `16KB`) to enable the zstd dictionary compression to increase the compression ratio. The actual store size can be lower than RocksDB. But the zstd dictionary compression can lead to about 10% throughput regression in a typical read-write workload.
 + 
 + Default value: `"0KB"`
 + Unit: KB|MB|GB