We keep the core component as private repo, which builds the ToplingZipTable files -- the SST with the searchable compression algo for speed. -- Although even without this component, ToplingDB is still outperforms RocksDB.
Sure, this is one of the reason we develop the framework of json/yaml conf and the embedded http server, with this framework, we discover several RocksDB bugs by this framework(we have contributed 100+ PRs and 60+ issues for RocksDB).
With embedded http server, all DB configurations and status are visually displayed, for example: the compaction progress, the SST file list with the compacting files are highlighted -- with different colors for different compaction jobs, different icons for different compaction types(https://github.com/topling/sideplugin-wiki-en/wiki/Compactio...)
It depends on workloads, in most cases, there is at least 3x perf gain. One of our customer get 20x perf gain(point search).
Another significant improvement is `select count(*) from SomeTable` in MyTopling, I optimized such query by 30x+ faster than MyRocks, 10x+ faster than InnoDB, while the multi-thread scaling is near linear -- better than InnoDB.
Yes, ToplingDB embeds an http server for showing DB info and online conf changes, this http server is very light weight and does not introduce any visible overhead.
-- prometheus is supported by this this http server.
Todis is a massive, persistent Redis server developed by Topling Inc which is a new start up company.
The Todis author was also the author of TerarkDB/Terark which was acquired by Bytedance at 2019.
Todis is Cloud Native, users can experiencing Managed Todis based on aliyun in 10 minutes.
The key features of todis are:
1. Computing and Storage are seperated for elastic scaling
2. Auto scaling, no need for sharding/partitioning
3. Elastic Distributed Compaction(feature of ToplingDB which forked from RocksDB)
4. Plenty (grafana) monitoring metrics
5. Web view for DB internal stats
reply