-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add key value separation feature to Nebula storage engine #3281
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Well done, LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good job, 👍
Codecov Report
@@ Coverage Diff @@
## master #3281 +/- ##
==========================================
+ Coverage 85.24% 85.26% +0.02%
==========================================
Files 1289 1289
Lines 120035 120113 +78
==========================================
+ Hits 102322 102414 +92
+ Misses 17713 17699 -14
Continue to review full report at Codecov.
|
# Whether or not to enable BlobDB (RocksDB key-value separation support) | ||
--rocksdb_enable_kv_separation=false | ||
# RocksDB key value separation threshold. Values at or above this threshold will be written to blob files during flush or compaction. | ||
--rocksdb_kv_separation_threshold=0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
if the threshold is set to zero, any writing will move to the blob file?
This PR exposes the key-value separation support of RocksDB in Nebula. Based on the experiment with internal dataset and testing environment, we can reduce query latency as much as 80%.