Closed stutiredboy closed 3 years ago
hi @stutiredboy Thanks for your feedback, kvrocks would auto-adjust the write_buffer_size
by calculating the key-value
size, see the related issue: https://github.com/bitleak/kvrocks/issues/118
As the second issue(the write buffer size from 16 to 16), we'll investigate and feedback here.
cc @karelrooted
I think we maybe should provide one config to enable auto-adjust of the write_buffer_size and memtable, instead of always enable, because, users maybe have their own method or optimization strategy such as munual config
yeah, also the second issue was a bug that we didn't update the config. I'll submit a new issue for @karelrooted .
the old write_buffer_size in the log is a typo(use the newly setted value as old value), the auto-resize-block-and-sst config directive is added in PR: https://github.com/bitleak/kvrocks/pull/289
Version: 2.0.1 @5f41145a
I set target_file_size_base and rocksdb.write_buffer_size to 128 in kvrocks.conf then use config get to double check the value was set to 128.
But, some minutes later, the value was changed to 16, log in kvrocks.INFO
We can find that
rocksdb.target_file_size_base
was changed to 16, thenrocksdb.write_buffer_size
was changed to the same asrocksdb.target_file_size_base
. And the most interesting isfrom 16 to 16
but notfrom 128 to 16
, I'm quite sure the value forrocksdb.write_buffer_size
in kvrocks.conf is 128 before kvrocks started.Questions: