OceanBase employs a shared‑nothing distributed cluster design where each node runs its own SQL, storage, and transaction engines, evolving through versions 0.5 to 4.0 to improve scalability, high availability, and low latency, while supporting multi‑tenant deployments and TPC‑C benchmark success.
Percona’s analysis of MySQL version adoption reveals a slow migration to 8.x, prompting extensive performance tests that compare default and tuned configurations of MySQL 5.7, 8.0.36, 8.4, Percona Server, and MariaDB using sysbench and TPC‑C benchmarks, with detailed results showing consistent performance regressions in newer releases.
An extensive benchmark compares MySQL 8.2 Community and Enterprise editions using sysbench and TPC‑C on identical EC2 instances, revealing that, under default configurations, the Enterprise edition offers no consistent performance advantage over the Community edition, with only occasional gains from optional plugins.
This article analyzes the popularity, success metrics, distributed versus centralized architectures, TPC‑C benchmark relevance, and a detailed feature comparison between MySQL and PostgreSQL, concluding which system currently leads in real‑world OLTP deployments.
This guide explains the background of TPC‑C, its key concepts, and provides a detailed, container‑based procedure for setting up the environment, preparing data, running the benchmark on RadonDB MySQL in Kubernetes, and interpreting throughput and price‑performance results.
This article explains the TPC‑C benchmark, covering its purpose, data model, database schema, the five transaction types, and a detailed step‑by‑step walkthrough of the New‑Order operation with accompanying SQL illustrations, while also summarizing workload characteristics and providing reference links.
This article introduces the TPC-C benchmark, its origin within the Transaction Processing Performance Council, the evolution from early standards like Debit Credit and TP1 to TPC-A, the structure of the TPC-C model with its nine tables and operations, and the subsequent development of newer standards such as TPC-E.
This article chronicles the ten‑year evolution of OceanBase, a distributed relational database created by Sun Zhenkun and his team, detailing early challenges, technical breakthroughs, benchmark victories like TPC‑C world records, and its impact on Alibaba’s financial systems.
OceanBase, Alibaba’s self‑developed distributed relational database, achieved world‑leading TPC‑C performance in 2019 and shattered its own record in 2020, a journey marked by intense team effort, architectural innovations like Paxos‑based scalability, and a vision to become a global database leader.
OceanBase achieved a new TPC‑C world record of 707 million tpmC using 1,557 cloud servers, demonstrating near‑linear horizontal scalability, significant single‑node performance gains, efficient parallel query processing, and a markedly lower cost per transaction compared with traditional high‑end hardware solutions.
The talk reviews the evolving challenges of enterprise databases, the shift toward distributed and cloud‑native architectures, and how OceanBase addresses high availability, scalability, hardware independence, and performance standards such as TPC‑C to meet modern financial and enterprise workloads.
The article presents a detailed technical overview of OceanBase, explaining why traditional centralized databases cannot meet modern OLTP and OLAP demands, how OceanBase achieves distributed transaction processing with Paxos‑based replication and majority voting for high availability, and how it validates its capabilities through the TPC‑C benchmark.
From a 2009 mandate to eliminate minicomputers to a 2019 TPC‑C world‑record, Alibaba’s decade‑long “de‑IOE” project forged OceanBase into a fully self‑developed, Oracle‑compatible database, delivering flexible architecture, talent growth, and massive cost savings while reshaping China’s IT landscape.
Over nine years, Ant Financial's OceanBase team transformed a fledgling distributed database into the first Chinese system to top the TPC‑C benchmark, beating Oracle's long‑standing record by more than double, while pioneering cloud‑based testing, intensive performance tuning, and a culture of relentless engineering dedication.
This article details OceanBase’s achievement in the TPC‑C benchmark, explaining the test architecture, the role of ODBC and OBProxy, and the various link‑layer performance, resource, and durability optimizations that enable high throughput and continuous service in a distributed database environment.
OceanBase’s distributed relational database achieved the top TPC‑C benchmark score by leveraging cloud‑native resources, optimized storage, advanced transaction engines, and extensive SQL tuning, with detailed insights into preparation, system architecture, performance testing phases, ACID compliance, and storage optimizations that set new industry standards.
OceanBase’s TPC‑C benchmark demonstrates how its distributed database achieves high durability, atomicity, isolation, and consistency on commodity cloud servers using Paxos‑based log replication, two‑phase commit, MVCC, and replicated tables, highlighting the architectural challenges and solutions for ACID compliance.
This article explains how OceanBase’s distributed, shared‑nothing architecture, with dual data replicas, Paxos‑based consistency, online compression, and resource‑isolated compaction, enables it to achieve top TPC‑C performance while addressing storage costs and CPU usage.
This article, the third in a five‑part series on OceanBase’s record‑breaking TPC‑C results, explains the SQL‑level challenges faced during the benchmark and details the optimizations—including stored procedures, LLVM‑based compilation, array binding, prepared statements, and updatable views—that enabled the performance gains.
This article provides a comprehensive technical analysis of OceanBase’s record‑breaking TPC‑C benchmark, covering the preparation work, test system design, planning, performance testing methodology, ACID verification, and the lessons learned from achieving 60.88 million tpmC on a distributed cloud platform.
This article provides a detailed technical analysis of OceanBase’s TPC‑C benchmark performance, covering the database’s development history, benchmark methodology, identified shortcomings, future improvement plans, and the strict standards and audit processes that ensure reliable OLTP benchmarking results.
OceanBase, the distributed database from Ant Financial, topped the latest TPC‑C benchmark, and this article explains the benchmark’s significance, the rigorous certification process, the performance and cost metrics, and how OceanBase’s architecture and Alibaba Cloud support enabled this achievement.
