[DOCS] Update dbStorage_writeCacheMaxSizeMb configuration description
Fixes #2500
### Motivation
The dbStorage_writeCacheMaxSizeMb configuration is not described clearly.
### Changes
Refine the description in the broker.conf file.
Reviewers: Enrico Olivelli <eolivelli@gmail.com>, Sijie Guo <None>
This closes #2502 from Jennifer88huang/master and squashes the following commits:
505527085 [Jinfeng Huang] update
0de963832 [Jinfeng Huang] update dbStorage_writeCacheMaxSizeMb
diff --git a/conf/bk_server.conf b/conf/bk_server.conf
index 4081920..64a7b48 100755
--- a/conf/bk_server.conf
+++ b/conf/bk_server.conf
@@ -659,8 +659,8 @@
# Size of Write Cache. Memory is allocated from JVM direct memory.
# Write cache is used to buffer entries before flushing into the entry log
-# For good performance, it should be big enough to hold a sub
-# dbStorage_writeCacheMaxSizeMb=512
+# For good performance, it should be big enough to hold a substantial amount of entries in the flush interval
+# By default it will be allocated to 25% of the available direct memory
# Size of Read cache. Memory is allocated from JVM direct memory.
# This read cache is pre-filled doing read-ahead whenever a cache miss happens
diff --git a/site/_data/config/bk_server.yaml b/site/_data/config/bk_server.yaml
index cd7b76f..f1a72c8 100644
--- a/site/_data/config/bk_server.yaml
+++ b/site/_data/config/bk_server.yaml
@@ -450,8 +450,8 @@
- name: DB Ledger Storage Settings
params:
- param: dbStorage_writeCacheMaxSizeMb
- description: Size of write cache. Memory is allocated from JVM direct memory. Write cache is used for buffer entries before flushing into the entry log. For good performance, it should be big enough to hold a sub.
- default: 512
+ description: Size of write cache. Memory is allocated from JVM direct memory. Write cache is used for buffer entries before flushing into the entry log. For good performance, it should be big enough to hold a substantial amount of entries in the flush interval.
+ default: 25% of the available direct memory
- param: dbStorage_readAheadCacheMaxSizeMb
description: Size of read cache. Memory is allocated from JVM direct memory. The read cache is pre-filled doing read-ahead whenever a cache miss happens.
default: 256
