KunlunBase is a distributed relational database management system(RDBMS) with complete NewSQL capabilities and robust transaction ACID guarantees and is compatible with standard SQL. Applications which used PostgreSQL or MySQL can work with KunlunBase as-is without any code change or rebuild because KunlunBase supports both PostgreSQL and MySQL connection protocols and DML SQL grammars. MySQL DBAs can quickly work on a KunlunBase cluster because we use MySQL as storage nodes of KunlunBase. KunlunBase can elastically scale out as needed, and guarantees transaction ACID under error conditions, and KunlunBase fully passes TPC-C, TPC-H and TPC-DS test suites, so it not only support OLTP workloads but also OLAP workloads. Application developers can use KunlunBase to build IT systems that handles terabytes of data, without any effort on their part to implement data sharding, distributed transaction processing, distributed query processing, crash safety, high availability, strong consistency, horizontal scalability. All these powerful features are provided by KunlunBase. KunlunBase supports powerful and user friendly cluster management, monitor and provision features, can be readily used as DBaaS.
2021-12-20 17:56:24: zhangjindong@zettadb.com created the issue
Currently, our commit pattern is sync commit, which means the commit request returns after commit finishes(ok or failure), this limits the throughput of the whole system.
Comparing to tidb sysbench results, our performance is bad when using mgr. This maybe majorly because we are using sync commit(forced by mgr), while tidb has the async commit pattern.
We need to consider whether to support 'async commit' for cases needing a big throughput while keeping the availability and durability of 3 replicas.
jd-zhang
commented
2 years ago
Issue migrated from trac ticket # 338 www.kunlunbase.com
component: computing nodes | priority: major
2021-12-20 17:56:24: zhangjindong@zettadb.com created the issue