@@ -58,7 +58,7 @@ db-path : ./db/
5858# but this will generate heavier IO load when flushing from buffer to disk,
5959# you should configure it based on you usage scenario.
6060# Supported Units [K|M|G], write-buffer-size default unit is in [bytes].
61- write-buffer-size : 256M
61+ write-buffer-size : 64M
6262
6363# The size of one block in arena memory allocation.
6464# If <= 0, a proper value is automatically calculated.
@@ -150,7 +150,7 @@ maxclients : 20000
150150# the price is that the number of sst files could be huge. On the contrary, the bigger the sst file size, the lower
151151# the performance and the higher the merge cost, while the number of files is fewer.
152152# Supported Units [K|M|G], target-file-size-base default unit is in [bytes] and the default value is 20M.
153- target-file-size-base : 20M
153+ target-file-size-base : 10M
154154
155155# Expire-time of binlog(write2file) files that stored within log-path.
156156# Any binlog(write2file) files that exceed this expire time will be cleaned up.
@@ -163,7 +163,7 @@ expire-logs-days : 7
163163# automatic cleaning will start to ensure the maximum number
164164# of binlog files is equal to expire-logs-nums.
165165# The [Minimum value] of this parameter is 10.
166- expire-logs-nums : 10
166+ expire-logs-nums : 3
167167
168168# The number of guaranteed connections for root user.
169169# This parameter guarantees that there are 2(By default) connections available
@@ -280,7 +280,7 @@ write-binlog : yes
280280# [NOTICE] Master and slaves must have exactly the same value for the binlog-file-size.
281281# The [value range] of binlog-file-size is [1K, 2G].
282282# Supported Units [K|M|G], binlog-file-size default unit is in [bytes] and the default value is 100M.
283- binlog-file-size : 104857600
283+ binlog-file-size : 10485760
284284
285285# Automatically triggers a small compaction according to statistics
286286# Use the cache to store up to 'max-cache-statistic-keys' keys
@@ -299,7 +299,7 @@ small-compaction-duration-threshold : 10000
299299# exceeds max-write-buffer-size when next write operation is issued.
300300# [RocksDB-Basic-Tuning](https://github.com/facebook/rocksdb/wiki/Setup-Options-and-Basic-Tuning)
301301# Supported Units [K|M|G], max-write-buffer-size default unit is in [bytes].
302- max-write-buffer-size : 10737418240
302+ max-write-buffer-size : 1073741824
303303
304304# The maximum number of write buffers(memtables) that are built up in memory for one ColumnFamily in DB.
305305# The default and the minimum number is 2. It means that Pika(RocksDB) will write to a write buffer
@@ -365,7 +365,7 @@ max-background-compactions : 2
365365max-background-jobs : 3
366366
367367# maximum value of RocksDB cached open file descriptors
368- max-cache-files : 5000
368+ max-cache-files : 1000
369369
370370# The ratio between the total size of RocksDB level-(L+1) files and the total size of RocksDB level-L files for all L.
371371# Its default value is 10(x). You can also change it to 5(x).
@@ -520,8 +520,8 @@ zset-cache-field-num-per-key : 512
520520# If zset-cache-start-direction is -1, cache the last 512[zset-cache-field-num-per-key] elements
521521zset-cache-start-direction : 0
522522
523- # the cache maxmemory of every db, configuration 10G
524- cache-maxmemory : 10737418240
523+ # the cache maxmemory of every db, configuration 512M
524+ cache-maxmemory : 536870912
525525
526526# cache-maxmemory-policy
527527# 0: volatile-lru -> Evict using approximated LRU among the keys with an expire set.
0 commit comments