From b039e63c6816ed371c6db975b4cbc7a3d170bb1f Mon Sep 17 00:00:00 2001 From: Zengran Zhang Date: Tue, 2 Apr 2019 22:03:45 +0800 Subject: [PATCH] kv: make delete range optional on number of keys Actually, we may only wanna let the objects with real big number of omap to use delete range. if not, we find too many tombstones will have side-effects on performance of kv. refer: https://github.com/facebook/rocksdb/wiki/DeleteRange-Implementation Signed-off-by: Zengran Zhang --- src/common/options.cc | 7 ++- src/kv/RocksDBStore.cc | 102 +++++++++++++++++++++++++++++++++++++---- src/kv/RocksDBStore.h | 4 +- 3 files changed, 102 insertions(+), 11 deletions(-) diff --git a/src/common/options.cc b/src/common/options.cc index 268f496d8f2e6..d5ecc21c1604b 100644 --- a/src/common/options.cc +++ b/src/common/options.cc @@ -3789,7 +3789,12 @@ std::vector