Re:TerarkDB, ByteDance's RocksDB replacement
by royguo1988 on Wednesday December 23, 2020 @01:49AM
(#25515120)
The reasons we did a better job(from our own perspective) than RocksDB are:
1. We moved lots of code out side db_mutex (db mutex is convenient but costs too much)
2. We introduced a new KV separation implementation that we believe is better than RocksDB’s implementation (we didn't hear any production user are using RocksDB's KV separation yet)
3. We introduced a lazy compaction strategy that can delay compaction task while online services are dealing with short-time heavy writing.
4. Other optimizations like time histogram based TTL, pipelined WAL sync.
[ Parent
| on HN ]
Re:TerarkDB, ByteDance's RocksDB replacement
by ddorian43 on Thursday December 24, 2020 @03:05AM
(#25525839)
There is https://pingcap.com/blog/titan-storage-engine-design-and-imp... that splits keys from values.