Change RocksDB to 7.х? #1013
Replies: 6 comments 6 replies
-
Thanks for @aleksraiden proposal, I think it'd be better to wait for more services using 7.x in production, or it also makes sense if we need requests which appears only in 7.x. |
Beta Was this translation helpful? Give feedback.
-
Hi @aleksraiden , |
Beta Was this translation helpful? Give feedback.
-
https://groups.google.com/g/rocksdb/c/umRPboha0as/m/5VP6zvwiCgAJ?utm_medium=email&utm_source=footer RocksDB community mentioned that 7.5.3 could significantly improve compaction time, so it may become one of the reasons to upgrade to 7.x, record it here first. |
Beta Was this translation helpful? Give feedback.
-
I think if we plan to upgrade to 7.x, as well just upgrade to the latest version |
Beta Was this translation helpful? Give feedback.
-
kvrocks with rocksdb_v6 vs rocksdv_v7 reportBuildbuild current kvrocks and use rocksdb-v7 kvrocks pr is xiaobiaozhao#4 Test stepsTest deploy stress script
kvrocks hardware settings
monitor
kvrocks-v7 vs kvrocks-v6 full compact monitor
172.27.255.229 disk monitor 172.27.255.230 disk monitor Other monitoring measures were consistent When kvrocks compacting
Conclusion
|
Beta Was this translation helpful? Give feedback.
-
Here is another patch in RocksDB 7.6: |
Beta Was this translation helpful? Give feedback.
-
So, after we are switched to C++17, we are ready to use an 7.х family of RocksDB. Maybe we can try to use 7.0.4 - as a latest version without any changes in public API sections, and then step-by-step migrate to newest versions?
I will submit PR, of course
Beta Was this translation helpful? Give feedback.
All reactions