Live data from Hacker News

TerarkDB, ByteDance's RocksDB replacement

github.com

1–10 of 84 posts

Re: TerarkDB, ByteDance's RocksDB replacement

#3

TerarkDB was acquired by Bytedance two years ago and is now using widely in Bytedance's database services. I am one of the maintainers of this project you can ask any question here.

Always love it when I see a maintainer offer clarifications in a HN comment section! What are the reasons for the perf improvements we see here?

Re: TerarkDB, ByteDance's RocksDB replacement

#7

TerarkDB was acquired by Bytedance two years ago and is now using widely in Bytedance's database services. I am one of the maintainers of this project you can ask any question here.

I think the performance images would be a lot more clear if they were on the same scale, as it stands it was unclear what was happening with, e.g. the disk write image until i zoomed into the axes.

Re: TerarkDB, ByteDance's RocksDB replacement

#9
post #8

TerarkDB was acquired by Bytedance two years ago and is now using widely in Bytedance's database services. I am one of the maintainers of this project you can ask any question here.

Why not merge the improvements into RocksDB itself?

There are mainly three reasons here:

1. We changed the source code too much that we are not able to merge it back to RocksDB easily (This project started at 2016 as an close-source project) 2. We have different road path with RocksDB (e.g. We will remove a lot of un-used code to make TerarkDB much more light-weight than current version in the future) 3. We have lots of third-party partners (e.g. Intel, on Opatane SSD/Memory and others with ZNS...) may participant in this project so we want to handle all commits ourself to make sure everything is under control.

Re: TerarkDB, ByteDance's RocksDB replacement

#10

TerarkDB was acquired by Bytedance two years ago and is now using widely in Bytedance's database services. I am one of the maintainers of this project you can ask any question here.

I think the performance images would be a lot more clear if they were on the same scale, as it stands it was unclear what was happening with, e.g. the disk write image until i zoomed into the axes.

Thanks for your suggestion, I will update the image soon
Post reply on HN